public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/46864] [4.5/4.6 Regression] ICE: verify_stmts failed: statement marked for throw, but doesn't with -fnon-call-exceptions Date: Thu, 09 Dec 2010 14:19:00 -0000 [thread overview] Message-ID: <bug-46864-4-HQ3jVM3iO5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46864-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46864 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-12-09 14:18:57 UTC --- This is execute_sm's fault, rewrite_mem_ref_loc doesn't call maybe_clean_eh_stmt. Adding that call fixes the ICE, but a) gimple_purge_dead_eh_edges isn't called (and can't be called immediately), and I don't see how the correct eh edges would be added for the load and store stmts that are added by store motion. So, I wonder if execute_sm just shouldn't give up optimizing if the mem ref might throw.
next prev parent reply other threads:[~2010-12-09 14:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-09 13:42 [Bug tree-optimization/46864] New: " zsojka at seznam dot cz 2010-12-09 14:19 ` jakub at gcc dot gnu.org [this message] 2010-12-09 14:35 ` [Bug tree-optimization/46864] " jakub at gcc dot gnu.org 2010-12-09 14:52 ` rguenth at gcc dot gnu.org 2010-12-09 20:16 ` jakub at gcc dot gnu.org 2010-12-10 12:42 ` jakub at gcc dot gnu.org 2010-12-10 12:45 ` [Bug tree-optimization/46864] [4.5 " jakub at gcc dot gnu.org 2011-01-16 20:16 ` jakub at gcc dot gnu.org 2011-01-17 8:38 ` jakub 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-46864-4-HQ3jVM3iO5@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).