public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/44982] [4.3/4.4/4.5/4.6 Regression] ICE in get_narrower, at tree.c:7832 Date: Fri, 17 Dec 2010 21:26:00 -0000 [thread overview] Message-ID: <bug-44982-4-twaDnNEw5x@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-44982-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44982 Steven Bosscher <steven at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu.org --- Comment #3 from Steven Bosscher <steven at gcc dot gnu.org> 2010-12-17 21:26:45 UTC --- I see no reason to cgraph_finalize_compilation_unit if there were parse errors. Richi, what do you think? Index: toplev.c =================================================================== --- toplev.c (revision 167996) +++ toplev.c (working copy) @@ -582,7 +582,12 @@ what's left of the symbol table output. */ timevar_pop (TV_PARSE); - if (flag_syntax_only || flag_wpa) + /* If all we have to do is syntax checking, or if there were parse + errors, stop here. */ + if (flag_syntax_only || seen_error) + return; + + if (flag_wpa) return; ggc_protect_identifiers = false; @@ -590,9 +595,6 @@ /* This must also call cgraph_finalize_compilation_unit. */ lang_hooks.decls.final_write_globals (); - if (seen_error ()) - return; - varpool_assemble_pending_decls (); finish_aliases_2 ();
next parent reply other threads:[~2010-12-17 21:26 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44982-4@http.gcc.gnu.org/bugzilla/> 2010-12-17 21:26 ` steven at gcc dot gnu.org [this message] 2010-12-18 20:22 ` rguenther at suse dot de 2011-06-27 13:55 ` [Bug middle-end/44982] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org 2012-03-13 14:14 ` [Bug middle-end/44982] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org 2012-07-02 13:53 ` [Bug middle-end/44982] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org 2013-04-12 15:17 ` [Bug middle-end/44982] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2014-06-12 13:45 ` [Bug middle-end/44982] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:38 ` [Bug middle-end/44982] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-01-15 1:22 ` tbsaunde at gcc dot gnu.org 2015-01-15 8:28 ` rguenther at suse dot de 2015-01-17 21:48 ` tbsaunde at gcc dot gnu.org 2015-06-23 8:21 ` [Bug middle-end/44982] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 20:10 ` [Bug middle-end/44982] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:36 ` jakub at gcc dot gnu.org 2010-07-19 0:26 [Bug c/44982] New: crash on invalid code if((a==1) ? (void) (0) : 1) soundis at infa dot fi 2010-07-19 9:13 ` [Bug middle-end/44982] [4.3/4.4/4.5/4.6 Regression] ICE in get_narrower, at tree.c:7832 rguenth at gcc dot gnu dot org 2010-07-19 9:58 ` steven at gcc dot gnu dot org 2010-07-22 8:56 ` rguenth at gcc dot gnu dot 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-44982-4-twaDnNEw5x@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).