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 tree-optimization/17517] [4.0 Regression] ICE: SSA corruption
Date: Thu, 16 Sep 2004 10:52:00 -0000 [thread overview]
Message-ID: <20040916105255.6195.qmail@sourceware.org> (raw)
In-Reply-To: <20040916101717.17517.steven@gcc.gnu.org>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-09-16 10:52 -------
Hmm, this is a recent regression, 3.5.0 20040909 cannot reproduce it
but 4.0.0 20040916 can. I cannot debug it as the 4.0.0 one is on openbsd and gdb support there is
worse than on darwin, gdb seg faults or internal errors. (and my linux server which used to build gcc is
down for some reason:( ).
I almost want to say this is a latent bug (in the sense it was present before 20040909 but did not show
in this testcase because SRA did not happen on the struct).
If I have time tommorrow I will try to reduce it on darwin where gdb actually works.
--
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |4.0.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17517
next prev parent reply other threads:[~2004-09-16 10:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 10:17 [Bug tree-optimization/17517] New: " steven at gcc dot gnu dot org
2004-09-16 10:18 ` [Bug tree-optimization/17517] " steven at gcc dot gnu dot org
2004-09-16 10:52 ` pinskia at gcc dot gnu dot org [this message]
2004-09-16 13:12 ` amacleod at redhat dot com
2004-09-16 13:32 ` belyshev at lubercy dot com
2004-09-16 16:20 ` stevenb at suse dot de
2004-09-16 16:26 ` amacleod at redhat dot com
2004-09-16 16:50 ` stevenb at suse dot de
2004-09-16 17:26 ` stevenb at suse dot de
2004-09-16 18:45 ` cvs-commit at gcc dot gnu dot org
2004-09-16 19:19 ` pinskia at gcc dot gnu dot org
2004-09-22 23:07 ` steven at gcc dot gnu dot org
2004-09-24 16:22 ` 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=20040916105255.6195.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).