public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "patrick.marlier at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/51280] New: ICE when lto1 does not have -fgnu-tm and object file uses TM Date: Wed, 23 Nov 2011 05:09:00 -0000 [thread overview] Message-ID: <bug-51280-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51280 Bug #: 51280 Summary: ICE when lto1 does not have -fgnu-tm and object file uses TM Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto AssignedTo: unassigned@gcc.gnu.org ReportedBy: patrick.marlier@gmail.com CC: aldyh@gcc.gnu.org, dnovillo@gcc.gnu.org, rguenth@gcc.gnu.org, rth@gcc.gnu.org, torvald@gcc.gnu.org LTO should display a error message to indicate that gnu-tm is not enabled and not ICE. lto1: internal compiler error: in streamer_get_builtin_tree, at tree-streamer-in.c:1056 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. 1051 if (fclass == BUILT_IN_NORMAL) 1052 { 1053 if (fcode >= END_BUILTINS) 1054 fatal_error ("machine independent builtin code out of range"); 1055 result = builtin_decl_explicit (fcode); 1056 gcc_assert (result); 1057 } (gdb) p fcode $2 = BUILT_IN_TM_COMMIT (gdb) bt #0 fancy_abort (file=0x12b2168 "../../trunk/gcc/tree-streamer-in.c", line=1056, function=0x12b2250 "streamer_get_builtin_tree") at ../../trunk/gcc/diagnostic.c:899 #1 0x0000000000c4f5ea in streamer_get_builtin_tree (ib=0x7fffffffd760, data_in=0x1a273d0) at ../../trunk/gcc/tree-streamer-in.c:1056 #2 0x00000000008b5aeb in lto_input_tree (ib=0x7fffffffd760, data_in=0x1a273d0) at ../../trunk/gcc/lto-streamer-in.c:1148 #3 0x00000000004b052a in lto_read_decls (decl_data=0x7ffff69b9000, data=0x1a36970, resolutions=0x1a26320) at ../../trunk/gcc/lto/lto.c:902 #4 0x00000000004b0e25 in lto_file_finalize (file_data=0x7ffff69b9000, file=0x19944a0) at ../../trunk/gcc/lto/lto.c:1140 #5 0x00000000004b0e72 in lto_create_files_from_ids (file=0x19944a0, file_data=0x7ffff69b9000, count=0x7fffffffd8ec) at ../../trunk/gcc/lto/lto.c:1150 #6 0x00000000004b0f8b in lto_file_read (file=0x19944a0, resolution_file=0x1a25460, count=0x7fffffffd8ec) at ../../trunk/gcc/lto/lto.c:1190 #7 0x00000000004b8095 in read_cgraph_and_symbols (nfiles=1, fnames=0x19af0f0) at ../../trunk/gcc/lto/lto.c:2591 #8 0x00000000004b87da in lto_main () at ../../trunk/gcc/lto/lto.c:2905 #9 0x00000000009ffe99 in compile_file () at ../../trunk/gcc/toplev.c:565 #10 0x0000000000a021a9 in do_compile () at ../../trunk/gcc/toplev.c:1931 #11 0x0000000000a02314 in toplev_main (argc=17, argv=0x197d2e0) at ../../trunk/gcc/toplev.c:2007 #12 0x00000000004bb7c4 in main (argc=17, argv=0x7fffffffda68) at ../../trunk/gcc/main.c:36 To reproduce, compile file with transactions and lto, and link without -flto. Patrick.
next reply other threads:[~2011-11-23 2:27 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-23 5:09 patrick.marlier at gmail dot com [this message] 2011-11-23 19:28 ` [Bug lto/51280] " patrick.marlier at gmail dot com 2011-12-09 18:16 ` aldyh at gcc dot gnu.org 2011-12-10 3:57 ` patrick.marlier at gmail dot com 2011-12-10 9:39 ` jakub at gcc dot gnu.org 2011-12-31 23:54 ` pinskia at gcc dot gnu.org 2012-01-16 13:25 ` aldyh at gcc dot gnu.org 2012-01-19 14:23 ` aldyh at gcc dot gnu.org 2012-01-19 14:23 ` aldyh 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-51280-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).