public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: james@jigsawdezign.com
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/8264: GCC3.2 Illegal Instruction building libgcc2.c
Date: Thu, 17 Oct 2002 13:06:00 -0000 [thread overview]
Message-ID: <20021017200246.22953.qmail@sources.redhat.com> (raw)
>Number: 8264
>Category: bootstrap
>Synopsis: GCC3.2 Illegal Instruction building libgcc2.c
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Oct 17 13:06:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: James A Wright
>Release: GCC3.2
>Organization:
>Environment:
AMD K6-2 450Mhz, 256Mb RAM
Linux 2.4.19
GLibc 2.2.4
>Description:
mkdir /unpacked/objdir
cd /unpacked/objdir
/unpacked/gcc3.2/configure
make bootstrap
Build fails with:
./xgcc -B./ -B/usr/local/i586-pc-linux-gnu/bin/ -isystem /usr/local/i586-pc-linux-gnu/include -isystem /usr/local/i586-pc-linux-gnu/sys-include -O2
-DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
-D__GCC_FLOAT_NOT_NEEDED -I. -I. -I/unpacked/gcc-3.2/gcc -I/unpacked/gcc-3.2/gcc/. -I/unpacked/gcc-3.2/gcc/config
-I/unpacked/gcc-3.2/gcc/../include -DL_floatdisf -c /unpacked/gcc-3.2/gcc/libgcc2.c -o libgcc/./_floatdisf.o
./xgcc -B./ -B/usr/local/i586-pc-linux-gnu/bin/ -isystem /usr/local/i586-pc-linux-gnu/include -isystem /usr/local/i586-pc-linux-gnu/sys-include -O2
-DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
-D__GCC_FLOAT_NOT_NEEDED -I. -I. -I/unpacked/gcc-3.2/gcc -I/unpacked/gcc-3.2/gcc/. -I/unpacked/gcc-3.2/gcc/config
-I/unpacked/gcc-3.2/gcc/../include -DL_fixunsdfsi -c /unpacked/gcc-3.2/gcc/libgcc2.c -o libgcc/./_fixunsdfsi.o
/unpacked/gcc-3.2/gcc/libgcc2.c: In function `__fixunsdfsi':
/unpacked/gcc-3.2/gcc/libgcc2.c:1173: internal error: Illegal instruction
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[3]: *** [libgcc/./_fixunsdfsi.o] Error 1
make[3]: Leaving directory `/unpacked/objdir/gcc'
make[2]: *** [libgcc.a] Error 2
make[2]: Leaving directory `/unpacked/objdir/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory `/unpacked/objdir/gcc'
make: *** [bootstrap] Error 2
[root@halcyon objdir]#
I'm sure it is not a hardware problem because it crashes in the same place everytime, and the same system has done numerous kernel builds without any problems...
>How-To-Repeat:
Fails same place everytime I try to rebuild GCC3.2 on this system...
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-10-17 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 13:06 james [this message]
2003-05-08 5:16 Dara Hazeghi
2003-05-08 10:40 giovannibajo
2003-05-09 6:46 Dara Hazeghi
2003-05-09 15:36 bangerth
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=20021017200246.22953.qmail@sources.redhat.com \
--to=james@jigsawdezign.com \
--cc=gcc-gnats@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).