public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uweigand at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/19865] [4.0 Regression] ice / gnat bug detected.
Date: Tue, 15 Feb 2005 05:48:00 -0000 [thread overview]
Message-ID: <20050214225038.8569.qmail@sourceware.org> (raw)
In-Reply-To: <20050209180751.19865.pluto@pld-linux.org>
------- Additional Comments From uweigand at gcc dot gnu dot org 2005-02-14 22:50 -------
(In reply to comment #5)
> The error occurs when building this with
> gnat1 -I<path-to-srcdir>/gcc/ada -O2 pr19865.adb
> (I've tested a gnat1 configured for s390-ibm-linux.)
I'm sorry, I have mixed up the include statements here.
Using this line, I do not get an ICE either. I do get
the ICE when using instead
gnat1 -I<path-to-builddir>/gcc/ada/rts -O2 pr19865.adb
(after I've built the Ada runtime library, of course).
This different include apparently causes gnat1 to use a
different method of exception handling, which is enough
of a difference to cause the ICE to vanish.
As to what causes the bug, as Andrew said the SRA pass
introduces a new temporary C.56 (in my case C.58), and
like in the other test case, the red-phi pass generates
a virtual operand (a VUSE in this case) for an unrenamed
C.58 in a function call:
<L4>:;
# VUSE <C.8_13>;
# VUSE <pr19865__no_argument_101>;
# VUSE <pr19865__cache_args__last_valX_102>;
# VUSE <pr19865__cache_args__tableX_103>;
# VUSE <FRAME.13_163>;
# VUSE <C.7_51>;
# VUSE <TMT.42_164>;
# VUSE <TMT.43_165>;
# VUSE <TMT.45_166>;
# VUSE <C.58>;
__gnat_rcheck_05 ("pr19865.adb", 37);
This subsequently aborts.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19865
next prev parent reply other threads:[~2005-02-14 22:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 23:35 [Bug ada/19865] New: " pluto at pld-linux dot org
2005-02-10 0:07 ` [Bug ada/19865] " mmazur at kernel dot pl
2005-02-10 0:33 ` [Bug ada/19865] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-02-10 12:24 ` awreynolds at mac dot com
2005-02-15 0:09 ` bosch at gcc dot gnu dot org
2005-02-15 1:23 ` pinskia at gcc dot gnu dot org
2005-02-15 1:32 ` dnovillo at gcc dot gnu dot org
2005-02-15 1:56 ` uweigand at gcc dot gnu dot org
2005-02-15 2:39 ` dnovillo at gcc dot gnu dot org
2005-02-15 3:14 ` pinskia at gcc dot gnu dot org
2005-02-15 4:20 ` dnovillo at gcc dot gnu dot org
2005-02-15 4:44 ` pinskia at gcc dot gnu dot org
2005-02-15 5:08 ` dnovillo at redhat dot com
2005-02-15 5:45 ` pinskia at gcc dot gnu dot org
2005-02-15 5:48 ` uweigand at gcc dot gnu dot org [this message]
2005-02-15 16:16 ` pinskia at gcc dot gnu dot org
2005-02-15 20:52 ` [Bug middle-end/19865] " uweigand at gcc dot gnu dot org
2005-02-16 19:17 ` dnovillo at redhat dot com
2005-02-17 0:16 ` cvs-commit at gcc dot gnu dot org
2005-02-17 0:16 ` dnovillo at gcc dot gnu dot org
2005-02-17 1:31 ` pinskia 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=20050214225038.8569.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).