public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schnetter at uni-tuebingen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/14928] [gfortran] minval intrinsic does not understand mask
Date: Fri, 04 Jun 2004 08:04:00 -0000	[thread overview]
Message-ID: <20040604080400.14791.qmail@sourceware.org> (raw)
In-Reply-To: <20040412204218.14928.schnetter@aei.mpg.de>


------- Additional Comments From schnetter at uni-tuebingen dot de  2004-06-04 08:03 -------
Section 13.2, "Arguments to intrinsic procedures" of the same draft, specifies 
that "the valid forms of reference for procedures with optional arguments are 
described in 12.4.1".  12.4.1 in turn describes "normal" (non-intrinsic) 
procedure calls, where the "name=" syntax is not compulsory. 
 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14928


  parent reply	other threads:[~2004-06-04  8:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-12 21:12 [Bug fortran/14928] New: " schnetter at aei dot mpg dot de
2004-04-12 21:52 ` [Bug fortran/14928] [gfortran] " pinskia at gcc dot gnu dot org
2004-04-13  4:14 ` pinskia at gcc dot gnu dot org
2004-04-13 10:11 ` schnetter at aei dot mpg dot de
2004-04-13 12:37 ` pinskia at gcc dot gnu dot org
2004-05-26 23:07 ` pinskia at gcc dot gnu dot org
2004-06-03 18:38 ` tobi at gcc dot gnu dot org
2004-06-03 22:07 ` schnetter at uni-tuebingen dot de
2004-06-03 22:23 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2004-06-04  8:04 ` schnetter at uni-tuebingen dot de [this message]
2004-06-04 22:40 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2004-06-05 13:11 ` [Bug fortran/14928] [gfortran] minloc " tobi at gcc dot gnu dot org
2004-06-14 15:56 ` cvs-commit at gcc dot gnu dot org
2004-06-14 16:06 ` tobi at gcc dot gnu dot org
2004-07-10  0:45 ` [Bug fortran/14928] " pinskia at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040604080400.14791.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).