public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/55660] [4.7/4.8 Regression] ICE instead of some warning during lto build with supplied different options (-funsigned-char vs none) Date: Wed, 12 Dec 2012 14:19:00 -0000 [thread overview] Message-ID: <bug-55660-4-e4OsnVd5GB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55660-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55660 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> 2012-12-12 14:18:46 UTC --- Ok, the issue is we preload char_type_node anyway, as show by Index: gcc/tree-streamer.c =================================================================== --- gcc/tree-streamer.c (revision 194444) +++ gcc/tree-streamer.c (working copy) @@ -237,6 +237,12 @@ streamer_tree_cache_lookup (struct strea static void record_common_node (struct streamer_tree_cache_d *cache, tree node) { + /* Verify we don't recursively pre-load nodes we do not want to preload. */ + gcc_assert (node != char_type_node + && node != boolean_type_node + && node != boolean_true_node + && node != boolean_false_node); + /* We have to make sure to fill exactly the same number of elements for all frontends. That can include NULL trees. As our hash table can't deal with zero entries we'll simply stream this is because we pre-load va_list_type_node (which is required, because we compare that by pointer equality). But the x86 backend (and possibly others) do: static tree ix86_build_builtin_va_list_abi (enum calling_abi abi) { tree f_gpr, f_fpr, f_ovf, f_sav, record, type_decl; /* For i386 we use plain pointer to argument area. */ if (!TARGET_64BIT || abi == MS_ABI) return build_pointer_type (char_type_node); oops.
next prev parent reply other threads:[~2012-12-12 14:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-12 6:40 [Bug lto/55660] New: ICE instead of some warning during lto build vbyakovl23 at gmail dot com 2012-12-12 9:55 ` [Bug lto/55660] [4.7/4.8 Regression] ICE instead of some warning during lto build with supplied different options (-funsigned-char vs none) rguenth at gcc dot gnu.org 2012-12-12 14:19 ` rguenth at gcc dot gnu.org [this message] 2012-12-13 11:13 ` rguenth at gcc dot gnu.org 2012-12-13 11:14 ` [Bug lto/55660] [4.7 " rguenth at gcc dot gnu.org 2013-02-04 12:05 ` rguenth at gcc dot gnu.org 2013-02-04 12:07 ` rguenth 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-55660-4-e4OsnVd5GB@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).