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 rtl-optimization/55740] [4.8 Regression] ICE in verify_loop_structure, at cfgloop.c:1582, error: loop 2's header does not belong directly to it Date: Wed, 19 Dec 2012 15:13:00 -0000 [thread overview] Message-ID: <bug-55740-4-tsCk0nqJbY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55740-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55740 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Component|middle-end |rtl-optimization AssignedTo|unassigned at gcc dot |rguenth at gcc dot gnu.org |gnu.org | --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> 2012-12-19 15:12:56 UTC --- And it's of course after RTL CSE ... Which ends up merging two loop headers as we cross-jumped the tails ... /* If we merge a loop header into its predecessor, update the loop structure. */ if (current_loops != NULL) { if (b->loop_father->header == b) { remove_bb_from_loops (a); add_bb_to_loop (a, b->loop_father); a->loop_father->header = a; } remove_bb_from_loops (b); } Which looks broken if a is already a loop header. I have a patch.
next prev parent reply other threads:[~2012-12-19 15:13 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-19 14:18 [Bug middle-end/55740] New: " rguenth at gcc dot gnu.org 2012-12-19 14:19 ` [Bug middle-end/55740] " rguenth at gcc dot gnu.org 2012-12-19 14:44 ` rguenth at gcc dot gnu.org 2012-12-19 14:56 ` rguenth at gcc dot gnu.org 2012-12-19 15:13 ` rguenth at gcc dot gnu.org [this message] 2012-12-20 12:46 ` [Bug rtl-optimization/55740] " rguenth at gcc dot gnu.org 2012-12-20 12:46 ` 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-55740-4-tsCk0nqJbY@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).