public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asharif at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/47447] [4.3/4.4 Regression] "Unable to coalesce ssa_names <x> and <y>" ICE in tree-ssa-coalesce.c when -O3 is used
Date: Thu, 03 Feb 2011 22:26:00 -0000	[thread overview]
Message-ID: <bug-47447-4-ShbhOaRNrG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47447-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from asharif at gcc dot gnu.org 2011-02-03 22:26:48 UTC ---
(In reply to comment #5)
> I almost want to say LOOP_VINFO_NITERS should not have abnormal SSA's to begin
> with.

Andrew, shouldn't it be fine to have abnormal SSAs as long as they don't
conflict? That may be the best solution -- i.e. bailing out only if they will
conflict later on, as opposed to what my patch does (it bails out as soon as an
abnormal name is detected).


  parent reply	other threads:[~2011-02-03 22:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 21:24 [Bug tree-optimization/47447] New: " asharif at gcc dot gnu.org
2011-01-25 11:10 ` [Bug tree-optimization/47447] [4.3/4.4 Regression] " rguenth at gcc dot gnu.org
2011-01-26 22:12 ` asharif at gcc dot gnu.org
2011-02-03 22:19 ` asharif at gcc dot gnu.org
2011-02-03 22:19 ` asharif at gcc dot gnu.org
2011-02-03 22:23 ` pinskia at gcc dot gnu.org
2011-02-03 22:25 ` asharif at gcc dot gnu.org
2011-02-03 22:26 ` asharif at gcc dot gnu.org [this message]
2011-03-01 19:40 ` asharif at gcc dot gnu.org
2011-06-27 10:41 ` rguenth at gcc dot gnu.org
2011-06-27 15:07 ` rguenth at gcc dot gnu.org
2012-03-13 16:23 ` [Bug tree-optimization/47447] [4.4 " jakub 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-47447-4-ShbhOaRNrG@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).