public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "t at sharklasers dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/66029] New: Build error compiling gcc5.1 using LTO Date: Tue, 05 May 2015 22:21:00 -0000 [thread overview] Message-ID: <bug-66029-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66029 Bug ID: 66029 Summary: Build error compiling gcc5.1 using LTO Product: gcc Version: 5.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: t at sharklasers dot com Target Milestone: --- Created attachment 35469 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35469&action=edit complete command line I compiled gcc5.1 without LTO optimizations and tried to compile it again with LTO using the new 5.1 compiler. "openSUSE 13.2 (Harlequin) (x86_64)" $ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=gcc5.1/lib/gcc/x86_64-unknown-linux-gnu/5.1.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ../gcc-5.1.0/configure --prefix=gcc5.1 --enable-languages=c,c++ --enable-gold=yes --enable-ld=yes --enable-lto --enable-bootstrap --disable-multilib Thread model: posix gcc version 5.1.0 (GCC) /usr/bin/ld: error in /tmp/cc4PfHUo.ltrans1.ltrans.o(.eh_frame); no .eh_frame_hdr table will be created. `_Unwind_Resume' referenced in section `.text' of /tmp/cc4PfHUo.ltrans1.ltrans.o: defined in discarded section `.text' of unwind-dw2.o (symbol from plugin) `_Unwind_Resume' referenced in section `.text' of /tmp/cc4PfHUo.ltrans3.ltrans.o: defined in discarded section `.text' of unwind-dw2.o (symbol from plugin) `_Unwind_Resume' referenced in section `.text' of /tmp/cc4PfHUo.ltrans3.ltrans.o: defined in discarded section `.text' of unwind-dw2.o (symbol from plugin) `_Unwind_Resume' referenced in section `.text.unlikely' of /tmp/cc4PfHUo.ltrans8.ltrans.o: defined in discarded section `.text' of unwind-dw2.o (symbol from plugin) collect2: error: ld returned 1 exit status Makefile:2606: recipe for target 'build/genmatch' failed
next reply other threads:[~2015-05-05 22:21 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-05 22:21 t at sharklasers dot com [this message] 2015-05-05 22:25 ` [Bug lto/66029] " t at sharklasers dot com 2015-05-05 23:24 ` hjl.tools at gmail dot com 2015-05-05 23:30 ` pinskia at gcc dot gnu.org 2015-05-06 14:15 ` t at sharklasers dot com 2015-05-06 14:17 ` t at sharklasers dot com 2015-05-06 14:21 ` trippels at gcc dot gnu.org 2015-05-06 14:48 ` hjl.tools at gmail dot com 2015-05-07 15:15 ` trippels at gcc dot gnu.org 2015-05-07 23:58 ` t at sharklasers dot com
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-66029-4@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).