public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30964] optional arguments to random_seed
Date: Sun, 12 Aug 2007 20:45:00 -0000	[thread overview]
Message-ID: <20070812204544.21866.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30964-10391@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from fxcoudert at gcc dot gnu dot org  2007-08-12 20:45 -------
Subject: Bug 30964

Author: fxcoudert
Date: Sun Aug 12 20:45:29 2007
New Revision: 127383

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127383
Log:
        PR fortran/30964
        PR fortran/33054

        * trans-expr.c (gfc_conv_function_call): When no formal argument
        list is available, we still substitute missing optional arguments.
        * check.c (gfc_check_random_seed): Correct the check on the
        number of arguments to RANDOM_SEED.
        * intrinsic.c (add_subroutines): Add a resolution function to
        RANDOM_SEED.
        * iresolve.c (gfc_resolve_random_seed): New function.
        * intrinsic.h (gfc_resolve_random_seed): New prototype.

        * intrinsics/random.c (random_seed): Rename into random_seed_i4.
        (random_seed_i8): New function.
        * gfortran.map (GFORTRAN_1.0): Remove _gfortran_random_seed,
        add _gfortran_random_seed_i4 and _gfortran_random_seed_i8.
        * libgfortran.h (iexport_proto): Replace random_seed by
        random_seed_i4 and random_seed_i8.
        * runtime/main.c (init): Call the new random_seed_i4.

        * gfortran.dg/random_4.f90: New test.
        * gfortran.dg/random_5.f90: New test.
        * gfortran.dg/random_6.f90: New test.
        * gfortran.dg/random_7.f90: New test.

Added:
    trunk/gcc/testsuite/gfortran.dg/random_4.f90
    trunk/gcc/testsuite/gfortran.dg/random_5.f90
    trunk/gcc/testsuite/gfortran.dg/random_6.f90
    trunk/gcc/testsuite/gfortran.dg/random_7.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/check.c
    trunk/gcc/fortran/intrinsic.c
    trunk/gcc/fortran/intrinsic.h
    trunk/gcc/fortran/iresolve.c
    trunk/gcc/fortran/trans-expr.c
    trunk/gcc/testsuite/ChangeLog
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/gfortran.map
    trunk/libgfortran/intrinsics/random.c
    trunk/libgfortran/libgfortran.h
    trunk/libgfortran/runtime/main.c


-- 


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


  parent reply	other threads:[~2007-08-12 20:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-25 21:16 [Bug fortran/30964] New: " tkoenig at gcc dot gnu dot org
2007-02-26  0:14 ` [Bug fortran/30964] " kargl at gcc dot gnu dot org
2007-02-26 19:53 ` tkoenig at gcc dot gnu dot org
2007-03-03 10:36 ` fxcoudert at gcc dot gnu dot org
2007-03-15 12:59 ` fxcoudert at gcc dot gnu dot org
2007-05-21 14:21 ` fxcoudert at gcc dot gnu dot org
2007-05-22  8:24 ` fxcoudert at gcc dot gnu dot org
2007-05-28 20:48 ` fxcoudert at gcc dot gnu dot org
2007-08-11 23:22 ` fxcoudert at gcc dot gnu dot org
2007-08-11 23:33 ` fxcoudert at gcc dot gnu dot org
2007-08-12  0:16 ` fxcoudert at gcc dot gnu dot org
2007-08-12 16:41 ` fxcoudert at gcc dot gnu dot org
2007-08-12 20:45 ` fxcoudert at gcc dot gnu dot org [this message]
2007-08-12 20:46 ` fxcoudert 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=20070812204544.21866.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).