public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zak at transversal dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/26195] New: pragma interface no longer handles explicit names Date: Thu, 09 Feb 2006 13:34:00 -0000 [thread overview] Message-ID: <bug-26195-1827@http.gcc.gnu.org/bugzilla/> (raw) If I compile the two files below, where the interface/implementation relationship is based on an explicitly-given name rather than the basename of the files, then no implementation appears to be produced. This occurs on both the 4.0 branch and trunk, and is a regression against 3.4.5. With 3.3.6: $ g++-3.3 -c -Wall -pedantic pragii2.cc && nm -A pragii2.o pragii2.o:00000000 W _ZN1AC1Ev pragii2.o:00000000 W _ZN1AC2Ev With 3.4.5: $ g++-3.4 -c -Wall -pedantic pragii2.cc && nm -A pragii2.o pragii2.o:00000000 W _ZN1AC1Ev pragii2.o:00000000 W _ZN1AC2Ev With recent 4.0 branch: $ /opt/gcc-svn/gcc-4_0-branch/bin/g++ -c -Wall -pedantic pragii2.cc && nm -A pragii2.o [no output] With recent trunk: $ /opt/gcc-svn/trunk/bin/g++ -c -Wall -pedantic pragii2.cc && nm -A pragii2.o [no output] /////////// // pragii.h #pragma interface "pragii-imaginary.h" struct A { A() { } }; /////////// ///////////// // pragii2.cc #pragma implementation "pragii-imaginary.h" #include "pragii.h" ///////////// Failing compiler versions: $ /opt/gcc-svn/gcc-4_0-branch/bin/g++ -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4_0-branch/configure --prefix=/opt/gcc-svn/gcc-4_0-branch --enable-threads --disable-libgcj --enable-languages=c,c++ Thread model: posix gcc version 4.0.3 20060209 (prerelease) $ /opt/gcc-svn/trunk/bin/g++ -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../trunk/configure --prefix=/opt/gcc-svn/trunk --enable-threads Thread model: posix gcc version 4.2.0 20060203 (experimental) -- Summary: pragma interface no longer handles explicit names Product: gcc Version: 4.0.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: zak at transversal dot com 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=26195
next reply other threads:[~2006-02-09 13:34 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-09 13:34 zak at transversal dot com [this message] 2006-02-10 15:00 ` [Bug c++/26195] " zak at transversal dot com 2006-02-10 15:53 ` zak at transversal dot com 2006-02-10 17:05 ` zak at transversal dot com 2006-02-13 18:47 ` [Bug c++/26195] [4.0 regression] " zak at transversal dot com 2006-02-13 18:48 ` [Bug c++/26195] [4.0/4.1/4.2 " pinskia at gcc dot gnu dot org 2006-02-13 22:18 ` mmitchel at gcc dot gnu dot org 2006-02-14 9:02 ` mmitchel at gcc dot gnu dot org 2006-02-14 12:08 ` zak at transversal dot com 2006-02-24 0:31 ` mmitchel at gcc dot gnu dot org 2006-03-01 15:57 ` zak at transversal dot com 2006-04-18 16:18 ` bonzini at gnu dot org 2006-05-25 2:40 ` mmitchel at gcc dot gnu dot org 2006-09-07 6:53 ` jason at gcc dot gnu dot org 2006-09-07 7:08 ` [Bug c++/26195] [4.0/4.1 " jason at gcc dot gnu dot org 2006-09-07 22:27 ` jason at gcc dot gnu dot org 2006-09-07 22:38 ` jason at gcc dot gnu dot org 2006-09-07 23:04 ` jason 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-26195-1827@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).