public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/65944] [5/6 Regression] FAIL: g++.dg/lto/pr65276: undefined reference to std2::exception::~exception() Date: Thu, 02 Jul 2015 09:48:00 -0000 [thread overview] Message-ID: <bug-65944-4-fSBcgwvgXs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65944-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65944 Christophe Lyon <clyon at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clyon at gcc dot gnu.org --- Comment #6 from Christophe Lyon <clyon at gcc dot gnu.org> --- Since this fix, I am observing this regression on arm* targets: cp_lto_pr65276_1.o (symbol from plugin): In function `typeinfo for std2::runtime_error': (.text+0x0): multiple definition of `typeinfo name for std2::exception' cp_lto_pr65276_0.o (symbol from plugin):(.text+0x0): first defined here cp_lto_pr65276_1.o (symbol from plugin): In function `typeinfo for std2::runtime_error': (.text+0x0): multiple definition of `typeinfo for std2::exception' cp_lto_pr65276_0.o (symbol from plugin):(.text+0x0): first defined here collect2: error: ld returned 1 exit status FAIL: g++.dg/lto/pr65276 cp_lto_pr65276_0.o-cp_lto_pr65276_1.o link, -flto -O0 -std=c++11
prev parent reply other threads:[~2015-07-02 9:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-30 9:05 [Bug testsuite/65944] New: " vries at gcc dot gnu.org 2015-04-30 11:18 ` [Bug testsuite/65944] " rguenth at gcc dot gnu.org 2015-06-17 10:12 ` [Bug testsuite/65944] [5/6 Regression] " uros at gcc dot gnu.org 2015-06-17 10:15 ` ubizjak at gmail dot com 2015-07-02 9:48 ` clyon at gcc dot gnu.org [this message]
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-65944-4-fSBcgwvgXs@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).