public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/59019] [4.9 regression] ICE in advance_target_bb, at sched-rgn.c:3561 Date: Fri, 08 Nov 2013 11:02:00 -0000 [thread overview] Message-ID: <bug-59019-4-mN0uM2yQpe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59019-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59019 --- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > Always considering trap-if as ending a BB appears to be a bit of a rathole. > Every time I squash one issue, another raises its head. A little unexpected I'd say, what kind of issues does that introduce? > I did find that combine.c already has some bits to recognize when it does > something that may muck up the CFG and tries to compensate, it just doesn't > hadle the situation around trap-if. > > I'm going to see if I can proof of concept a fix in that code. Of course > this is a pass specific fix, but as I look deeper, more memories keep coming > back -- we've had special code in cse.c to deal with similar situations, so > maybe adding another case for combine isn't that bad after all. See existing examples in split_all_insns and lra.
next prev parent reply other threads:[~2013-11-08 11:02 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-06 10:48 [Bug rtl-optimization/59019] New: " schwab@linux-m68k.org 2013-11-06 11:39 ` [Bug rtl-optimization/59019] " rguenth at gcc dot gnu.org 2013-11-07 6:46 ` law at redhat dot com 2013-11-07 7:20 ` ebotcazou at gcc dot gnu.org 2013-11-07 17:22 ` ebotcazou at gcc dot gnu.org 2013-11-08 11:02 ` ebotcazou at gcc dot gnu.org [this message] 2013-11-08 23:15 ` steven at gcc dot gnu.org 2013-11-15 22:19 ` law at redhat dot com 2013-11-18 18:07 ` law at redhat dot com
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-59019-4-mN0uM2yQpe@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).