public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67039] Documentation of pseudorandom number intrinsics is incorrect
Date: Wed, 30 Sep 2015 22:20:00 -0000	[thread overview]
Message-ID: <bug-67039-4-qk7nL9kxcp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67039-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67039

--- Comment #5 from kargl at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #4)
> > > Resolved as WONTFIX?
> >
> > Probably not.  See the last 2 paragraphs in comment #1.
> 
> Sorry, but my question was motivated by the reading of these two
> paragraphs!-(
> Thus two more explicit questions:
> 
> (1) Shall I submit a patch to replace in the manual all the "Fortran 95 and
> later" with "Fortran 90 and later" where appropriate?

No.  gfortran never tried to address the Fortran 90 standard.
Whatever is stated in F90 is irrelevant to the extent that 
gfortran is a Fortran 95 compiler and F90 beget F95.

> 
> (2) Shall I submit a patch to replace 
> 
> The Fortran 2003 standard specifies the intrinsic RANDOM_SEED to initialize 
> the pseudo-random numbers generator and RANDOM_NUMBER to generate 
> pseudo-random numbers.
> 
> with
> 
> The Fortran 9? standard specifies the intrinsic RANDOM_SEED to initialize
> the pseudo-random numbers generator and RANDOM_NUMBER to generate 
> pseudo-random numbers. These intrinsics should be used in new codes.
> 

I would not not call out a particular standard version.  Probably
something like 

 The Fortran standard specifies the intrinsic subroutine RANDOM_SEED
 to initialize the pseudo-random numbers generator and the intrinsic
 subroutine RANDOM_NUMBER to generate pseudo-random numbers.  These
 subroutines should be used in new codes.


      parent reply	other threads:[~2015-09-30 22:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28  3:27 [Bug fortran/67039] New: " spam.brian.taylor at gmail dot com
2015-07-28  6:17 ` [Bug fortran/67039] " kargl at gcc dot gnu.org
2015-08-29 15:21 ` dominiq at lps dot ens.fr
2015-08-29 15:48 ` kargl at gcc dot gnu.org
2015-08-30 10:34 ` dominiq at lps dot ens.fr
2015-09-30 22:20 ` kargl at gcc dot gnu.org [this message]

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=bug-67039-4-qk7nL9kxcp@http.gcc.gnu.org/bugzilla/ \
    --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).