public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/30081] New: Interface bug overloading random_seed, random_number Date: Wed, 06 Dec 2006 09:11:00 -0000 [thread overview] Message-ID: <bug-30081-6318@http.gcc.gnu.org/bugzilla/> (raw) Hi, here's an interface related bug I discovered which is not yet mentioned in PR 29670. % gfortran gfcbug46.f90 gfcbug46.f90:25.29: call random_number (t% x) 1 Error: There is no specific subroutine for the generic 'random_number' at (1) gfcbug46.f90:20.29: call random_seed (size=n) 1 Error: There is no specific subroutine for the generic 'random_seed' at (1) The code is standard-conforming and works with other compilers. See the attached code for details. -- Summary: Interface bug overloading random_seed, random_number Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: anlauf at gmx dot de GCC host triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30081
next reply other threads:[~2006-12-06 9:11 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-06 9:11 anlauf at gmx dot de [this message] 2006-12-06 9:12 ` [Bug fortran/30081] " anlauf at gmx dot de 2006-12-07 17:28 ` pault at gcc dot gnu dot org 2006-12-07 18:50 ` burnus at gcc dot gnu dot org 2006-12-14 21:13 ` pault at gcc dot gnu dot org 2006-12-14 21:14 ` pault at gcc dot gnu dot org 2006-12-16 1:40 ` patchapp at dberlin dot org 2006-12-20 13:48 ` pault at gcc dot gnu dot org 2006-12-21 8:49 ` anlauf at gmx dot de 2006-12-31 15:01 ` [Bug fortran/30081] [4.2 and 4.1 only ] " pault at gcc dot gnu dot org 2006-12-31 15:18 ` [Bug fortran/30081] [4.1 " pault at gcc dot gnu dot org 2007-01-10 18:58 ` 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=bug-30081-6318@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: linkBe 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).