public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/62026] [4.9/4.10 Regression] Crash in lto_get_decl_name_mapping Date: Sat, 09 Aug 2014 14:55:00 -0000 [thread overview] Message-ID: <bug-62026-4-9zaMiGM57m@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62026-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62026 Markus Trippelsdorf <trippels at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2014-08-09 CC| |trippels at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #2 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- Also happens during Firefox libxul link: markus@x4 library % cat minimal /var/tmp/moz-build-dir/toolkit/library/../../dom/ipc/TabChild.o /var/tmp/moz-build-dir/toolkit/library/../../widget/xpwidgets/nsContentProcessWidgetFactory.o /var/tmp/moz-build-dir/toolkit/library/../../widget/xpwidgets/nsIdleService.o /var/tmp/moz-build-dir/toolkit/library/../../widget/xpwidgets/nsScreenManagerProxy.o /var/tmp/moz-build-dir/toolkit/library/../../widget/xpwidgets/nsTransferable.o /var/tmp/moz-build-dir/toolkit/library/../../widget/gtk/nsWidgetFactory.o /var/tmp/moz-build-dir/toolkit/library/../../widget/gtk/nsWindow.o markus@x4 library % c++ -w -flto -pipe -O3 -shared -Wfatal-errors @minimal lto1: internal compiler error: Segmentation fault 0x91a64f crash_signal ../../gcc/gcc/toplev.c:337 0x81df58 lto_get_decl_name_mapping(lto_file_decl_data*, char const*) ../../gcc/gcc/lto-section-in.c:340 0x8174a6 copy_function_or_variable ../../gcc/gcc/lto-streamer-out.c:2162 0x8180f1 lto_output() ../../gcc/gcc/lto-streamer-out.c:2254 0x862601 write_lto ../../gcc/gcc/passes.c:2226 0x865b11 ipa_write_optimization_summaries(lto_symtab_encoder_d*) ../../gcc/gcc/passes.c:2423 0x5424ba do_stream_out ../../gcc/gcc/lto/lto.c:2457 0x544d39 stream_out ../../gcc/gcc/lto/lto.c:2499 0x544d39 lto_wpa_write_files ../../gcc/gcc/lto/lto.c:2636 0x54d24a do_whole_program_analysis ../../gcc/gcc/lto/lto.c:3304 0x54d24a lto_main() ../../gcc/gcc/lto/lto.c:3424 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. lto-wrapper: fatal error: /var/tmp/gcc_test/usr/local/bin/c++ returned 1 exit status compilation terminated. /usr/bin/ld: fatal error: lto-wrapper failed collect2: error: ld returned 1 exit status The attached testcase doesn't reproduce the issue for me.
next prev parent reply other threads:[~2014-08-09 14:55 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-62026-4@http.gcc.gnu.org/bugzilla/> 2014-08-05 19:30 ` d.g.gorbachev at gmail dot com 2014-08-06 8:58 ` rguenth at gcc dot gnu.org 2014-08-09 14:55 ` trippels at gcc dot gnu.org [this message] 2014-08-17 5:27 ` [Bug lto/62026] [4.9/5 " d.g.gorbachev at gmail dot com 2014-08-29 8:40 ` trippels at gcc dot gnu.org 2014-08-29 9:46 ` smf.linux at ntlworld dot com 2014-08-29 10:06 ` trippels at gcc dot gnu.org 2014-08-29 12:54 ` smf.linux at ntlworld dot com 2014-09-03 11:57 ` jamborm at gcc dot gnu.org 2014-09-14 14:57 ` smf.linux at ntlworld dot com 2014-09-14 14:59 ` smf.linux at ntlworld dot com 2014-09-14 15:42 ` trippels at gcc dot gnu.org 2014-09-23 11:21 ` jamborm at gcc dot gnu.org 2014-09-23 11:38 ` trippels at gcc dot gnu.org 2014-10-04 22:00 ` hubicka at gcc dot gnu.org 2014-10-05 2:53 ` [Bug lto/62026] [5 " hubicka at gcc dot gnu.org 2014-10-15 17:00 ` trippels at gcc dot gnu.org 2014-10-15 17:01 ` hubicka at gcc dot gnu.org 2014-10-15 17:18 ` trippels at gcc dot gnu.org 2014-10-15 18:06 ` 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-62026-4-9zaMiGM57m@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).