public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/64163] [5 Regression] r218024 causes qt5 build failure Date: Wed, 03 Dec 2014 22:18:00 -0000 [thread overview] Message-ID: <bug-64163-4-H1JalTSMBN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64163-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64163 Alan Modra <amodra at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amodra at gmail dot com --- Comment #6 from Alan Modra <amodra at gmail dot com> --- No, this is not a gold bug on x86_64. ld.bfd may link without complaint, but the resulting shared library will crash, I think. There are calls to _ZN5QListI7QStringED1Ev which resolve to 0 (ie. the ELF header in the shared lib). This seems to be a fairly recent bug. On x86_64, 20141126 and 20141203 miscompile the unreduced testcase while 20141111 looks to be OK. You can easily see whether there is a problme by running nm *.o | grep _ZN5QListI7QStringED 0000000000000000 W _ZN5QListI7QStringED2Ev 0000000000000000 n _ZN5QListI7QStringED5Ev 0000000000000000 W _ZN5QListI7QStringED1Ev 0000000000000000 W _ZN5QListI7QStringED2Ev 0000000000000000 n _ZN5QListI7QStringED5Ev If as above you see only one copy of _ZN5QListI7QStringED1Ev, then only one of the two comdat groups define that symbol.
next prev parent reply other threads:[~2014-12-03 22:18 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-03 7:57 [Bug ipa/64163] New: " trippels at gcc dot gnu.org 2014-12-03 8:00 ` [Bug ipa/64163] " pinskia at gcc dot gnu.org 2014-12-03 8:03 ` jakub at gcc dot gnu.org 2014-12-03 8:11 ` trippels at gcc dot gnu.org 2014-12-03 8:46 ` trippels at gcc dot gnu.org 2014-12-03 10:06 ` rguenth at gcc dot gnu.org 2014-12-03 16:59 ` trippels at gcc dot gnu.org 2014-12-03 22:18 ` amodra at gmail dot com [this message] 2014-12-04 7:17 ` trippels at gcc dot gnu.org 2014-12-04 19:33 ` hjl.tools at gmail dot com 2014-12-11 11:45 ` rguenth at gcc dot gnu.org 2015-01-16 4:59 ` hubicka at gcc dot gnu.org 2015-01-16 11:13 ` trippels at gcc dot gnu.org 2015-01-16 11:23 ` trippels at gcc dot gnu.org 2015-01-18 9:52 ` trippels at gcc dot gnu.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-64163-4-H1JalTSMBN@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).