public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wjp at usecode dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/43905] New: duplicate __PRETTY_FUNCTION__ symbol for functions differing in const-ness Date: Tue, 27 Apr 2010 00:44:00 -0000 [thread overview] Message-ID: <bug-43905-19092@http.gcc.gnu.org/bugzilla/> (raw) When compiling the attached lll.ii file (from lll.c from the gfan maths package at http://www.math.tu-berlin.de/~jensen/software/gfan/gfan.html ) with g++ 4.5.0, I get the following error message: g++ -O2 lll.ii -c -o lll.o /tmp/ccRt1FUj.s: Assembler messages: /tmp/ccRt1FUj.s:5145: Error: symbol `_ZZN6MatrixIiEixEPiPP6VektorIiEiE19__PRETTY_FUNCTION__' is already defined The error is not triggered with -O1, but it is triggered with -O1 -fipa-sra. Looking at the generated .s, the problem appears to be that the same XXX__PRETTY_FUNCTION__ symbol is generated for both an operator[] and its const version. g++ -v: Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/usr/local/gcc-4.5.0/libexec/gcc/x86_64-unknown-linux-gnu/4.5.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /usr/local/gcc-4.5.0/src/gcc-4.5.0/configure --enable-languages=c,c++,fortran --with-gnu-as --with-gnu-as=/usr/local/binutils-2.20.1/bin/as --with-gnu-ld --with-ld=/usr/local/binutils-2.20.1/bin/ld --with-gmp=/usr/local/mpir-1.2.2 --with-mpfr=/usr/local/mpfr-2.4.2 --with-mpc=/usr/local/mpc-0.8.1 --prefix=/usr/local/gcc-4.5.0 Thread model: posix gcc version 4.5.0 (GCC) -- Summary: duplicate __PRETTY_FUNCTION__ symbol for functions differing in const-ness Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: wjp at usecode dot org GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: x86_64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43905
next reply other threads:[~2010-04-27 0:44 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-04-27 0:44 wjp at usecode dot org [this message] 2010-04-27 0:48 ` [Bug c++/43905] " wjp at usecode dot org 2010-04-27 0:53 ` [Bug tree-optimization/43905] " pinskia at gcc dot gnu dot org 2010-04-27 2:09 ` pinskia at gcc dot gnu dot org 2010-04-27 9:30 ` [Bug tree-optimization/43905] [4.5/4.6 Regression] " rguenth at gcc dot gnu dot org 2010-05-19 12:53 ` rguenth at gcc dot gnu dot org 2010-06-10 21:39 ` jamborm at gcc dot gnu dot org 2010-06-14 12:44 ` jamborm at gcc dot gnu dot org 2010-06-16 12:22 ` jamborm at gcc dot gnu dot org 2010-06-24 11:58 ` [Bug tree-optimization/43905] [4.5 " jakub at gcc dot gnu dot org 2010-06-29 13:16 ` jamborm at gcc dot gnu dot org 2010-06-30 13:27 ` jamborm at gcc dot gnu dot org 2010-07-02 13:28 ` jamborm 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-43905-19092@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).