public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/20606] ICE in make_edges, at cfgbuild.c:327 on x86_64 (with O2 - not with no optimizations)
Date: Tue, 03 May 2005 16:38:00 -0000 [thread overview]
Message-ID: <20050503163641.4956.qmail@sourceware.org> (raw)
In-Reply-To: <20050323182431.20606.overholt@redhat.com>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-03 16:36 -------
(In reply to comment #8)
> We no longer fail with this code on the mainline but most likely because actually thread the jump
> which I was taking in comment #5.
Let me rewrite that.
This now works on the mainline. This is most likely due to the jump threading changes in which we
actually catch the threading on the tree level instead of waiting until the RTL level which causes the
bug.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20606
next prev parent reply other threads:[~2005-05-03 16:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 18:24 [Bug java/20606] New: " overholt at redhat dot com
2005-03-23 18:25 ` [Bug java/20606] " overholt at redhat dot com
2005-03-23 18:27 ` [Bug middle-end/20606] " pinskia at gcc dot gnu dot org
2005-03-23 18:50 ` pinskia at gcc dot gnu dot org
2005-03-23 18:56 ` pinskia at gcc dot gnu dot org
2005-03-23 19:29 ` pinskia at gcc dot gnu dot org
2005-03-23 19:38 ` pinskia at gcc dot gnu dot org
2005-03-23 19:46 ` pinskia at gcc dot gnu dot org
2005-03-23 20:30 ` pinskia at gcc dot gnu dot org
2005-04-06 15:14 ` aph at gcc dot gnu dot org
2005-05-03 15:11 ` aph at gcc dot gnu dot org
2005-05-03 16:11 ` aph at gcc dot gnu dot org
2005-05-03 16:16 ` pinskia at gcc dot gnu dot org
2005-05-03 16:38 ` pinskia at gcc dot gnu dot org [this message]
2005-08-08 19:27 ` mmkernel at ezplanet dot net
2005-08-08 19:37 ` aph at gcc dot gnu dot org
2005-08-24 15:01 ` overholt at redhat dot com
2005-09-30 22:30 ` pinskia at gcc dot gnu dot org
2005-10-01 4:36 ` pinskia at gcc dot gnu dot org
[not found] <bug-20606-9773@http.gcc.gnu.org/bugzilla/>
2005-10-02 18:40 ` pinskia at gcc dot gnu dot org
2005-10-04 19:07 ` pinskia at gcc dot gnu dot org
2005-10-04 19:14 ` pinskia at gcc dot gnu dot org
2005-10-04 19:18 ` pinskia at gcc dot gnu dot org
2005-10-05 0:55 ` pinskia at gcc dot gnu dot org
2005-10-05 13:24 ` pinskia at gcc dot gnu dot org
2005-10-05 19:50 ` cvs-commit at gcc dot gnu dot org
2005-10-05 19:52 ` pinskia at gcc dot gnu dot org
2005-10-05 19:52 ` cvs-commit at gcc dot gnu dot 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=20050503163641.4956.qmail@sourceware.org \
--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).