public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "spam.brian.taylor at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67039] New: Documentation of pseudorandom number intrinsics is incorrect
Date: Tue, 28 Jul 2015 03:27:00 -0000	[thread overview]
Message-ID: <bug-67039-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 67039
           Summary: Documentation of pseudorandom number intrinsics is
                    incorrect
           Product: gcc
           Version: 5.2.0
            Status: UNCONFIRMED
          Severity: trivial
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: spam.brian.taylor at gmail dot com
  Target Milestone: ---

The gfortran documentation for the RANDOM_NUMBER and RANDOM_SEED subroutines
indicates that they are part of Fortran 95 and later.  In fact, they were
included in the Fortran 90 standard.

The gfortran documentation for the SRAND subroutine, a GNU extension, includes
in the "Notes" section the following: "The Fortran 2003 standard specifies the
intrinsic RANDOM_SEED to initialize the pseudo-random numbers generator and
RANDOM_NUMBER to generate pseudo-random numbers."  The reference here should be
to the Fortran 90 standard, not 2003.

https://gcc.gnu.org/onlinedocs/gcc-5.2.0/gfortran/RANDOM_005fNUMBER.html#RANDOM_005fNUMBER

https://gcc.gnu.org/onlinedocs/gcc-5.2.0/gfortran/RANDOM_005fSEED.html#RANDOM_005fSEED

https://gcc.gnu.org/onlinedocs/gcc-5.2.0/gfortran/SRAND.html#SRAND


             reply	other threads:[~2015-07-28  3:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28  3:27 spam.brian.taylor at gmail dot com [this message]
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

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@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).