public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincenzo.innocente at cern dot ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/47247] Linker plugin specification makes it difficult to handle COMDATs Date: Thu, 10 May 2012 07:32:00 -0000 [thread overview] Message-ID: <bug-47247-4-3e5ThuFumz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47247-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47247 vincenzo Innocente <vincenzo.innocente at cern dot ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vincenzo.innocente at cern | |dot ch --- Comment #27 from vincenzo Innocente <vincenzo.innocente at cern dot ch> 2012-05-10 07:14:51 UTC --- is all this in 4.7? with GNU gold (GNU Binutils 2.21.1) 1.11 and gcc-4_7-branch revision 187326 with linker-plugin enabled I get this type of errors ld: error: hidden symbol '_ZThn16_N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_errorEEED0Ev' is not defined locally ld: /tmp/innocent/ccggD26x.ltrans8.ltrans.o: in function _ZTVN5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_errorEEEE.local.4390:ccggD26x.ltrans8.o(.data.rel.ro+0x1558): warning: relocation refers to discarded section does not occur w/o linker-plugin is the problem on gcc or gold side? (posted also in http://sourceware.org/bugzilla/show_bug.cgi?id=12488)
next prev parent reply other threads:[~2012-05-10 7:16 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-10 16:51 [Bug lto/47247] New: " hubicka at gcc dot gnu.org 2011-01-10 17:02 ` [Bug lto/47247] " hubicka at gcc dot gnu.org 2011-01-10 17:11 ` hjl.tools at gmail dot com 2011-01-10 17:12 ` hjl.tools at gmail dot com 2011-01-10 17:13 ` hubicka at ucw dot cz 2011-01-10 17:19 ` hjl.tools at gmail dot com 2011-01-10 18:20 ` hubicka at gcc dot gnu.org 2011-01-10 18:36 ` hjl.tools at gmail dot com 2011-01-10 19:06 ` ccoutant at gcc dot gnu.org 2011-01-10 19:08 ` ccoutant at gcc dot gnu.org 2011-01-10 21:27 ` hjl.tools at gmail dot com 2011-01-10 21:27 ` hubicka at gcc dot gnu.org 2011-02-14 20:34 ` rafael.espindola at gmail dot com 2011-02-15 18:51 ` hubicka at ucw dot cz 2011-02-15 19:45 ` rafael.espindola at gmail dot com 2011-02-16 0:23 ` hubicka at ucw dot cz 2011-02-16 4:04 ` rafael.espindola at gmail dot com 2011-02-16 7:59 ` hubicka at ucw dot cz 2011-02-16 16:23 ` rafael.espindola at gmail dot com 2011-02-16 23:13 ` Jan Hubicka 2011-02-16 23:18 ` hubicka at ucw dot cz 2011-02-16 23:37 ` ccoutant at google dot com 2011-02-17 1:25 ` rafael.espindola at gmail dot com 2011-08-27 18:16 ` hubicka at gcc dot gnu.org 2011-09-26 21:47 ` ccoutant at gcc dot gnu.org 2011-09-27 0:23 ` ccoutant at gcc dot gnu.org 2011-09-28 13:09 ` hubicka at gcc dot gnu.org 2011-10-02 10:42 ` hubicka at gcc dot gnu.org 2012-05-10 7:32 ` vincenzo.innocente at cern dot ch [this message] 2012-05-10 7:54 ` rguenth at gcc dot gnu.org 2012-05-10 8:52 ` vincenzo.innocente at cern dot ch 2012-05-10 16:06 ` vincenzo.innocente at cern dot ch 2012-05-10 17:10 ` hubicka at ucw dot cz 2012-05-10 17:17 ` vincenzo.innocente at cern dot ch 2012-05-12 14:37 ` hubicka at gcc dot gnu.org 2012-05-14 8:13 ` vincenzo.innocente at cern dot ch
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-47247-4-3e5ThuFumz@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).