public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/38066] bug6 ambiguous reference Date: Tue, 11 Nov 2008 15:26:00 -0000 [thread overview] Message-ID: <20081111152528.22709.qmail@sourceware.org> (raw) In-Reply-To: <bug-38066-15125@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from burnus at gcc dot gnu dot org 2008-11-11 15:25 ------- > Error: Name 'getnullset' at (1) is an ambiguous reference to > 'getnullset' from module 'pbit4set' I have not yet checked the source, but other compilers give similar errors: * NAG f95: Error: bug6M.f90, line 17: Symbol GETNULLSET found both in module PBIT4SET and in PBIT8SET detected at CALL@GETNULLSET Error: bug6M.f90, line 17: Symbol GETNULLSET found both in module PBIT4SET and in PBIT8SET detected at CALL@GETNULLSET * g95: In file bug6M.f90:22 END MODULE Bug6 1 Error: Name 'getnullset' at (1) is an ambiguous reference to 'getnullset' from module 'pbit4set' * ifort: bug6M.f90(17): error #6405: The same named entity from different modules and/or program units cannot be referenced. [GETNULLSET] CALL GetNullSet (search_set) * openf95: openf95-486 openf95: ERROR SUB_A, File = bug6M.f90, Line = 17, Column = 12 "GETNULLSET" has been use associated from module "PBIT4SET" and at least one more module. It must not be referenced. > The NAG, Intel and g95 compilers all compile this code. Hmm, not here! You have in bug6M.f90: USE PBit4Set USE PBit8Set That makes the following two getNullSet available: pure subroutine getNullSet (ANullSet) ! In pbit4setM.f90 type (TPBit4Set), intent(out) :: ANullSet pure subroutine getNullSet (ANullSet) ! In pbit8setM.f90 type (TPBit8Set), intent(out) :: ANullSet If you now call "getNullSet" you have a problem since getNullSet exists in both PBit4Set and PBit8Set. (Note: "getNullSet" is *not* a generic interface.) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38066
next prev parent reply other threads:[~2008-11-11 15:26 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-09 15:04 [Bug fortran/38066] New: " clerman at fuse dot net 2008-11-09 15:05 ` [Bug fortran/38066] " clerman at fuse dot net 2008-11-11 15:26 ` burnus at gcc dot gnu dot org [this message] 2008-11-11 16:08 ` clerman at fuse dot net 2008-11-11 19:34 ` burnus at gcc dot gnu dot org 2008-11-11 23:20 ` clerman at fuse dot net 2008-11-11 23:23 ` clerman at fuse dot net 2008-11-20 13:44 ` mikael at gcc dot gnu dot org 2008-11-24 2:19 ` clerman at fuse dot net 2008-11-28 21:04 ` dfranke 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=20081111152528.22709.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: 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).