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 middle-end/67005] [5/6 Regression] ICE: in verify_loop_structure, at cfgloop.c:1647 (loop with header n not in loop tree) Date: Tue, 25 Aug 2015 09:07:00 -0000 [thread overview] Message-ID: <bug-67005-4-sXNCljztYA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67005-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67005 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- Note we already do /* If we made a BB unconditionally exit a loop then this transform alters the set of BBs in the loop. Schedule a fixup. */ if (loop_exit_edge_p (bb->loop_father, e)) loops_state_set (LOOPS_NEED_FIXUP); remove_edge (e2); thus this would need to add sth like || e2->flags & IRREDUCIBLE_LOOP
next prev parent reply other threads:[~2015-08-25 9:07 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-67005-4@http.gcc.gnu.org/bugzilla/> 2015-07-27 8:12 ` rguenth at gcc dot gnu.org 2015-08-25 8:59 ` mpolacek at gcc dot gnu.org 2015-08-25 9:06 ` rguenth at gcc dot gnu.org 2015-08-25 9:07 ` rguenth at gcc dot gnu.org [this message] 2015-08-25 11:49 ` mpolacek at gcc dot gnu.org 2015-08-25 12:57 ` mpolacek at gcc dot gnu.org 2015-08-25 14:49 ` mpolacek at gcc dot gnu.org 2015-08-27 17:08 ` mpolacek at gcc dot gnu.org 2015-08-27 17:08 ` mpolacek at gcc dot gnu.org 2015-08-28 9:34 ` rguenth at gcc dot gnu.org 2015-08-31 11:31 ` mpolacek at gcc dot gnu.org 2015-08-31 12:46 ` mpolacek 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-67005-4-sXNCljztYA@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).