public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <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, 15 Nov 2013 22:19:00 -0000	[thread overview]
Message-ID: <bug-59019-4-E5hdajh9we@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 #8 from Jeffrey A. Law <law at redhat dot com> ---
This has gone latent.  Regardless it's relatively easy to fix things up in
combine -- which does similar kinds of things when it's able to collapse a
conditional jump to an unconditional jump and the like.  I'm testing that now
(with a hack that exposes this bug again to ensure the combine.c bits get
exercised).

Basically we just have to remove the now dead insns from the block, zap the
outgoing edges and emit the barrier.

Steven, the reason conditional traps are not considered control flow altering
is that in the event of a trap, then stop execution.  If the condition is
false, they carry-on.  I can see both sides the "they should be considered
control flow altering" -- I'm not passionate enough about either to make a big
deal of it.

Eric, in the chaos of the last few days, I didn't save any of the spots that I
had to change to make conditional traps control flow altering.  I went through
3 or 4 places that needed fixing, then decide to look at working within the
current scheme by fixing up combine...


  parent reply	other threads:[~2013-11-15 22:19 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
2013-11-08 23:15 ` steven at gcc dot gnu.org
2013-11-15 22:19 ` law at redhat dot com [this message]
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-E5hdajh9we@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: link
Be 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).