public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "abel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/56957] [4.9 regression] ICE in add_insn_after, at emit-rtl.c:3783
Date: Thu, 18 Apr 2013 09:18:00 -0000	[thread overview]
Message-ID: <bug-56957-4-L0rbPpLOtv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56957-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56957

--- Comment #7 from Andrey Belevantsev <abel at gcc dot gnu.org> 2013-04-18 09:18:17 UTC ---
(In reply to comment #6)
> (In reply to comment #5)
> > Created attachment 29886 [details]
> > proposed patch
> 
> You should probably make this a static inline function and add a comment
> with a rationale ;-)

Actually I've made the full-blown function, the reason being that I forgot that
we keep the history vector sorted, so it's not enough to check only the last
element, you'd need to check all of them.  Took some time from digging this
from Itanium slow testing though :-) I will add a comment, sure.


  parent reply	other threads:[~2013-04-18  9:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14 19:40 [Bug rtl-optimization/56957] New: " schwab@linux-m68k.org
2013-04-15 10:12 ` [Bug rtl-optimization/56957] " rguenth at gcc dot gnu.org
2013-04-16 20:22 ` steven at gcc dot gnu.org
2013-04-16 20:35 ` steven at gcc dot gnu.org
2013-04-16 20:54 ` steven at gcc dot gnu.org
2013-04-16 21:36 ` steven at gcc dot gnu.org
2013-04-17  5:14 ` abel at gcc dot gnu.org
2013-04-17  6:52 ` abel at gcc dot gnu.org
2013-04-18  9:08 ` steven at gcc dot gnu.org
2013-04-18  9:18 ` abel at gcc dot gnu.org [this message]
2013-04-22  9:48 ` abel at gcc dot gnu.org
2013-04-25 10:03 ` abel at gcc dot gnu.org
2013-04-30 10:58 ` abel 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-56957-4-L0rbPpLOtv@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).