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/48389] [4.5/4.6/4.7 Regression] ICE: in make_edges, at cfgbuild.c:319 with -mtune=pentiumpro
Date: Thu, 07 Apr 2011 15:05:00 -0000	[thread overview]
Message-ID: <bug-48389-4-lJAFADLoM3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48389-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Jeffrey A. Law <law at redhat dot com> 2011-04-07 15:04:49 UTC ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/06/11 17:00, steven at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48389
> 
> --- Comment #5 from Steven Bosscher <steven at gcc dot gnu.org> 2011-04-06 23:00:31 UTC ---
> Created attachment 23905
>   --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23905
> First shot at a fix (also for PR48486)
> 
> Well, one can always hope for a quick fix.
I was looking at your proposed patch -- the first thing that jumps out
is cfgbuild.c has many tests similar to the one you fixed (testing for
eq/ne without masking off irrelevant bits).

I'd hate to see this once instance get fixed and all the others left
behind, but I'm also not familiar enough with the code to say for sure
if the other tests are correct as-written or definitely need to be fixed.

The cfgexpand changes look pretty reasonable.  The extra barrier is odd,
but not terribly surprising given the wacky way we've represented jump
tables in RTL.

It's not clear why you twiddled the code to mask off EDGE_EXECUTABLE,
but it's not terribly important, just a curiosity on my part.

jeff

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNndKIAAoJEBRtltQi2kC7fAgH/3A9Rsa28p2Kkly/eZAf5kBU
aGFO3XbeC/MfarJQM7AdQ33WVFL+bAr2DBUaxXE304WGM0T4S/jwEPOiYbeJ2Bsi
ziXZfa3urRgC10zAVSqAbP8y40NLqC3aO9NL9o+OB6eyjWuDSPTDakOpmWNJOqGg
A3oAg5ONWcJO5CxODIUBaXlJBtV7igGNjrQnSPouKOCC8lR+Ljy8yQK62kMR6pP3
h7hJzhEr09wWpq5rd5rEekZd9xvboPGChvD5QK6BMHtE6HdM2UVJ7Z02X8EgKUJj
J8oCGd4RK6fsRWvO00fAZBeev2ccz5zjKhlry4QiXm9tNHwN8n0Xff2k32jEFgs=
=cObX
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2011-04-07 15:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 16:11 [Bug rtl-optimization/48389] New: " zsojka at seznam dot cz
2011-04-06  0:26 ` [Bug rtl-optimization/48389] " pinskia at gcc dot gnu.org
2011-04-06 16:53 ` law at redhat dot com
2011-04-06 16:55 ` law at redhat dot com
2011-04-06 20:42 ` steven at gcc dot gnu.org
2011-04-06 21:53 ` steven at gcc dot gnu.org
2011-04-06 22:51 ` law at redhat dot com
2011-04-06 23:00 ` steven at gcc dot gnu.org
2011-04-07 15:05 ` law at redhat dot com [this message]
2011-04-07 15:38 ` matz at gcc dot gnu.org
2011-04-07 18:41 ` law at redhat dot com
2011-04-07 21:28 ` stevenb.gcc at gmail dot com
2011-04-08 11:38 ` matz at gcc dot gnu.org
2011-04-08 13:05 ` matz at gcc dot gnu.org
2011-04-08 20:20 ` matz at gcc dot gnu.org
2011-04-08 20:22 ` [Bug rtl-optimization/48389] [4.5/4.6 " matz at gcc dot gnu.org
2011-04-09 10:09 ` stevenb.gcc at gmail dot com
2011-04-10 10:46 ` rguenth at gcc dot gnu.org
2011-04-28 15:18 ` rguenth at gcc dot gnu.org
2012-07-02 11:30 ` rguenth at gcc dot gnu.org
2013-04-12 16:18 ` [Bug rtl-optimization/48389] [4.6 " 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-48389-4-lJAFADLoM3@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).