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: Wed, 06 Apr 2011 22:51:00 -0000 [thread overview]
Message-ID: <bug-48389-4-QreqnobawF@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 #4 from Jeffrey A. Law <law at redhat dot com> 2011-04-06 22:51:26 UTC ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/06/11 15:52, steven at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48389
>
> --- Comment #3 from Steven Bosscher <steven at gcc dot gnu.org> 2011-04-06 21:52:54 UTC ---
> OK, not quite. We somehow have a barrier _inside_ a basic block, and that's
> somehow a problem after the patch but not before?!
I tried to warn you that it wasn't as easy as just moving hte call to
rebuild_jump_labels :-)
jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNnO5iAAoJEBRtltQi2kC7y1kH/R+nRv2iL79CgbPFxWYBTX44
6Fb7f72e6VdymlXu3xOSvkQ3em+4AdWzjay9o5UWRIQSFUuFgS41Yc9z/UR0uqQd
OVwdX56kDFJaDfCX0XLjtddjiMN2js2jxiiXlGr1nq2sprWGFEabRxSmU6KqhN+Z
hdrXH18h2nOe9KjVfshZrUgM80UxhykorjuWo7d+TBwARU21C051OSRwvAYr7I3o
anYEBBzAvw2RzRyyUOVzVi24ErTyY+ZIn2wXJp9mIJmHKsdZMZCzYz4RGLysmnw5
gyzR6NsOU6st0K4SsLSqMWBIBddP5QI5Z+wEMiYUiu7Qto8lC3uE8xE3Edf7ja8=
=2qbJ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-04-06 22:51 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 [this message]
2011-04-06 23:00 ` steven at gcc dot gnu.org
2011-04-07 15:05 ` law at redhat dot com
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-QreqnobawF@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).