From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc@gcc.gnu.org
Subject: [lno] bootstrap failure
Date: Wed, 31 Mar 2004 05:58:00 -0000 [thread overview]
Message-ID: <200403302359.i2UNxVJD018270@relay.rwth-aachen.de> (raw)
Hi,
since roughly a week ago I cannot bootstrap the lno-branch on i86-pc-linux-gnu,
since I'm getting the following ICE:
make[2]: Entering directory `/Work/reichelt/gccbuild/src-lno/build/gcc'
stage1/xgcc -Bstage1/ -B/home/reichelt/GCC/FARM/gcc-lno-20040330/i686-pc-linux-gnu/bin/ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wold-style-definition -Wno-variadic-macros -Werror -fno-common -DHAVE_CONFIG_H -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I../../gcc/gcc/../libbanshee/libcompat -I../../gcc/gcc/../libbanshee -I../../gcc/gcc/../libbanshee/points-to -c insn-extract.c \
-o insn-extract.o
insn-extract.c: In function `insn_extract':
insn-extract.c:16: internal compiler error: in ggc_recalculate_in_use_p, at ggc-page.c:1590
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[2]: *** [insn-extract.o] Error 1
make[2]: Leaving directory `/Work/reichelt/gccbuild/src-lno/build/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory `/Work/reichelt/gccbuild/src-lno/build/gcc'
make: *** [bootstrap-lean] Error 2
I ran configure with
../gcc/configure --enable-threads --enable-checking --prefix=/home/reichelt/GCC/FARM/gcc-lno-20040330
Alas I cannot provide preprocessed sources, because the bugs goes away if
I add -save-temps (but then I'm getting comparison failures later).
Is anybody else seeing this?
Regards,
Volker
next reply other threads:[~2004-03-30 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 5:58 Volker Reichelt [this message]
2004-03-31 8:20 ` Zdenek Dvorak
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=200403302359.i2UNxVJD018270@relay.rwth-aachen.de \
--to=reichelt@igpm.rwth-aachen.de \
--cc=gcc@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).