public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at tat dot physik dot uni-tuebingen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/13882] ICE on compiling unwind-ia64.c during stage1
Date: Thu, 18 Mar 2004 10:06:00 -0000 [thread overview]
Message-ID: <20040318100642.21333.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040127104224.13882.rguenth@tat.physik.uni-tuebingen.de>
------- Additional Comments From rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-18 10:06 -------
Subject: Re: ICE on compiling unwind-ia64.c during
stage1
On Thu, 18 Mar 2004, giovannibajo at libero dot it wrote:
>
> ------- Additional Comments From giovannibajo at libero dot it 2004-03-18 02:40 -------
> Jan, could you please have a look, and at least confirm this bug if you can
> reproduce it?
Still happens for me with 3.4 branch as of 2004 Mar 18.
Configuring with
--enable-languages="c,c++,f77" --enable-threads=posix
--enable-__cxa_atexit --disable-libunwind-exceptions --disable-checking
make profiledbootstrap
fails with
./xgcc -B./ -B/home/rguenth/ia64/gcc3.4-180304/ia64-unknown-linux-gnu/bin/
-isystem /home/rguenth/ia64/gcc3.4-180304/ia64-unknown-linux-gnu/include
-isystem
/home/rguenth/ia64/gcc3.4-180304/ia64-unknown-linux-gnu/sys-include
-L/tmp/gcc-obj/gcc/../ld -O2 -DIN_GCC -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem
./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
-D__GCC_FLOAT_NOT_NEEDED -I. -I. -I/home/rguenth/src/gcc/gcc3.4/gcc
-I/home/rguenth/src/gcc/gcc3.4/gcc/.
-I/home/rguenth/src/gcc/gcc3.4/gcc/../include -fexceptions -c
/home/rguenth/src/gcc/gcc3.4/gcc/config/ia64/unwind-ia64.c -o
libgcc/./unwind-ia64.o
/home/rguenth/src/gcc/gcc3.4/gcc/config/ia64/unwind-ia64.c: In function
`dup_state_stack':
/home/rguenth/src/gcc/gcc3.4/gcc/config/ia64/unwind-ia64.c:395: internal
compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
i.e. instrumented compiler ICEs in compiling gcc/config/ia64/unwind-ia64.c
Richard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13882
next prev parent reply other threads:[~2004-03-18 10:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 10:42 [Bug c/13882] New: " rguenth at tat dot physik dot uni-tuebingen dot de
2004-01-27 10:44 ` [Bug c/13882] " rguenth at tat dot physik dot uni-tuebingen dot de
2004-01-27 13:15 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-01-27 14:08 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-01-27 15:36 ` [Bug optimization/13882] " pinskia at gcc dot gnu dot org
2004-03-16 16:26 ` pinskia at gcc dot gnu dot org
2004-03-18 2:40 ` giovannibajo at libero dot it
2004-03-18 10:06 ` rguenth at tat dot physik dot uni-tuebingen dot de [this message]
2004-06-05 18:01 ` [Bug rtl-optimization/13882] " pinskia at gcc dot gnu dot org
2004-06-21 16:25 ` pinskia at gcc dot gnu dot org
2004-08-03 22:20 ` [Bug rtl-optimization/13882] ICE on compiling unwind-ia64.c during stage1 (profiledbootstrap) pinskia at gcc dot gnu dot org
2004-08-05 16:44 ` pinskia at gcc dot gnu dot org
2004-08-16 22:03 ` wilson at gcc dot gnu dot org
2004-08-17 0:14 ` wilson 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=20040318100642.21333.qmail@sources.redhat.com \
--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).