public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "olchansk at panix dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/16485] New: Private subroutines from different modules collide during linking. Date: Mon, 12 Jul 2004 00:45:00 -0000 [thread overview] Message-ID: <20040712004514.16485.olchansk@panix.com> (raw) gfortran version "gcc version 3.5.0 20040710 (experimental)" generates incorrect names for private functions inside modules, causing link-time collisions between same-named private functions from different modules: (this problem prevents this example from even assembling): [olchansk@tw15 gfortran_test]$ cat test_ldcollide.f90 module foo private contains subroutine sub end subroutine sub end module foo module bar private contains subroutine sub end subroutine sub end module bar [olchansk@tw15 gfortran_test]$ make test_ldcollide.o /triumfcs/trshare/olchansk/gcc-tree-ssa/install/bin/gfortran -x f95 -c -o test_ldcollide.o -O2 -g -Wall -Waliasing -Wline-truncation -Wsurprising -Wunused-labels -fPIC -ffixed-line-length-132 test_ldcollide.f90 /tmp/ccAzTdiq.s: Assembler messages: /tmp/ccAzTdiq.s:30: Error: symbol `sub_' is already defined make: *** [test_ldcollide.o] Error 1 K.O. -- Summary: Private subroutines from different modules collide during linking. Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: olchansk at panix dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16485
next reply other threads:[~2004-07-12 0:45 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-12 0:45 olchansk at panix dot com [this message] 2004-07-12 4:39 ` [Bug fortran/16485] " olchansk at panix dot com 2004-07-12 6:25 ` pinskia at gcc dot gnu dot org 2004-07-12 12:37 ` tobi at gcc dot gnu dot org 2004-07-13 17:19 ` tobi at gcc dot gnu dot org 2004-09-02 10:51 ` tobi at gcc dot gnu dot org 2004-09-15 13:13 ` cvs-commit at gcc dot gnu dot org 2004-09-15 13:16 ` pbrook at gcc dot gnu dot org 2004-11-06 15:43 ` 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=20040712004514.16485.olchansk@panix.com \ --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).