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/55329] [4.8 Regression] ICE: internal compiler error: in operator[], at vec.h:487 with -O -fno-guess-branch-probability -fnon-call-exceptions --param=early-inlining-insns=111 Date: Thu, 15 Nov 2012 16:31:00 -0000 [thread overview] Message-ID: <bug-55329-4-Ei8EyQbNfK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55329-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55329 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org |gnu.org | --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-11-15 16:31:10 UTC --- Created attachment 28701 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28701 gcc48-pr55329.patch Untested fix. The problem is that clearing bits in a bitmap while it is being iterated using EXECUTE_IF_SET_IN_BITMAP is dangerous and can't work reliably, in this case the bitmap contained just a single bit, that got cleared and replaced by a smaller bit (the clearing removed the only bitmap_element, setting reused it with different index (smaller) with higher bits set in it). In gimple_purge_all_dead_eh_edges it is just a few extra instructions to process the forwarder blocks (it quickly finds out that they don't have any EDGE_EH edges and does nothing for them), so IMHO it doesn't matter much if we don't clear those bits. On the other side, if there could be multiple forwarder blocks, we might risk we don't handle them correctly, as they could have bb's with lower indexes as successors.
next prev parent reply other threads:[~2012-11-15 16:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-14 20:51 [Bug tree-optimization/55329] New: " zsojka at seznam dot cz 2012-11-14 21:22 ` [Bug tree-optimization/55329] " dominiq at lps dot ens.fr 2012-11-15 11:26 ` jakub at gcc dot gnu.org 2012-11-15 11:29 ` hubicka at gcc dot gnu.org 2012-11-15 16:31 ` jakub at gcc dot gnu.org [this message] 2012-11-16 22:05 ` jakub at gcc dot gnu.org 2012-11-19 9:46 ` 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-55329-4-Ei8EyQbNfK@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).