public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dougmencken at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/42347] [4.5/4.6 Regression] sched-deps.c:3840:1: internal compiler error: in fixup_reorder_chain, at cfglayout.c:796
Date: Sun, 09 May 2010 14:56:00 -0000 [thread overview]
Message-ID: <20100509145648.32050.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42347-18266@http.gcc.gnu.org/bugzilla/>
------- Comment #17 from dougmencken at gmail dot com 2010-05-09 14:56 -------
../.././gcc -I../.././gcc/. -I../.././gcc/../include
-I../.././gcc/../libcpp/include -I../.././gcc/../libdecnumber
-I../.././gcc/../libdecnumber/dpd -I../libdecnumber ../.././gcc/rtlhooks.c
-o rtlhooks.o
/root/build-farm/gcc-4.5.0.srcpkg/host-powerpc-gnu-linux-uclibc/prev-gcc/xgcc
-B/root/build-farm/gcc-4.5.0.srcpkg/host-powerpc-gnu-linux-uclibc/prev-gcc/
-B/usr/powerpc-gnu-linux-uclibc/bin/ -B/usr/powerpc-gnu-linux-uclibc/bin/
-B/usr/powerpc-gnu-linux-uclibc/lib/ -isystem
/usr/powerpc-gnu-linux-uclibc/include -isystem
/usr/powerpc-gnu-linux-uclibc/sys-include -c -g -O2 -gtoggle -DIN_GCC -W
-Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes
-Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -Wold-style-definition -Wc++-compat -DHAVE_CONFIG_H
-I. -I. -I../.././gcc -I../.././gcc/. -I../.././gcc/../include
-I../.././gcc/../libcpp/include -I../.././gcc/../libdecnumber
-I../.././gcc/../libdecnumber/dpd -I../libdecnumber ../.././gcc/sbitmap.c
-o sbitmap.o
/root/build-farm/gcc-4.5.0.srcpkg/host-powerpc-gnu-linux-uclibc/prev-gcc/xgcc
-B/root/build-farm/gcc-4.5.0.srcpkg/host-powerpc-gnu-linux-uclibc/prev-gcc/
-B/usr/powerpc-gnu-linux-uclibc/bin/ -B/usr/powerpc-gnu-linux-uclibc/bin/
-B/usr/powerpc-gnu-linux-uclibc/lib/ -isystem
/usr/powerpc-gnu-linux-uclibc/include -isystem
/usr/powerpc-gnu-linux-uclibc/sys-include -c -g -O2 -gtoggle -DIN_GCC -W
-Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes
-Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -Wold-style-definition -Wc++-compat -DHAVE_CONFIG_H
-I. -I. -I../.././gcc -I../.././gcc/. -I../.././gcc/../include
-I../.././gcc/../libcpp/include -I../.././gcc/../libdecnumber
-I../.././gcc/../libdecnumber/dpd -I../libdecnumber
../.././gcc/sched-deps.c -o sched-deps.o
../.././gcc/sched-deps.c: In function 'get_dep_weak_1':
../.././gcc/sched-deps.c:3841:1: internal compiler error: in
fixup_reorder_chain, at cfglayout.c:796
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[3]: *** [sched-deps.o] Error 1
make[3]: Leaving directory
`/root/build-farm/gcc-4.5.0.srcpkg/host-powerpc-gnu-linux-uclibc/gcc'
make[2]: *** [all-stage2-gcc] Error 2
make[2]: Leaving directory `/root/build-farm/gcc-4.5.0.srcpkg'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory `/root/build-farm/gcc-4.5.0.srcpkg'
make: *** [all] Error 2
Command exited with non-zero status 2
real 7h 47m 02s
user 5h 39m 43s
sys 13m 48.43s
----
Tried to bootstrap GCC 4.5.0. Again.
"How TO REPRODUCE IT WITH CROSS COMPILER"? No way. Just try to build it native.
And not on x86 (i386, i486, i586, i586mmx, i686, ........, x86_64,
x86_64_4cores, ......). AGAIN: NOT ON intel compatible x86 or 100% compatible
amd or intel compatible.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42347
next prev parent reply other threads:[~2010-05-09 14:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 10:15 [Bug bootstrap/42347] New: " dougmencken at gmail dot com
2009-12-10 10:55 ` [Bug bootstrap/42347] " dougmencken at gmail dot com
2009-12-10 12:09 ` [Bug bootstrap/42347] [4.5 Regression] " rguenth at gcc dot gnu dot org
2009-12-11 23:12 ` rguenth at gcc dot gnu dot org
2010-01-23 11:53 ` dougmencken at gmail dot com
2010-01-23 12:06 ` steven at gcc dot gnu dot org
2010-04-03 17:39 ` siarhei dot siamashka at gmail dot com
2010-04-03 21:54 ` siarhei dot siamashka at gmail dot com
2010-04-06 11:01 ` siarhei dot siamashka at gmail dot com
2010-04-06 11:08 ` steven at gcc dot gnu dot org
2010-04-06 11:25 ` rguenth at gcc dot gnu dot org
2010-04-06 14:44 ` siarhei dot siamashka at gmail dot com
2010-04-27 17:07 ` [Bug bootstrap/42347] [4.5/4.6 " dougmencken at gmail dot com
2010-04-27 19:14 ` dougmencken at gmail dot com
2010-04-28 9:16 ` rguenth at gcc dot gnu dot org
2010-04-29 19:36 ` armin76 at gentoo dot org
2010-05-03 23:45 ` siarhei dot siamashka at gmail dot com
2010-05-04 7:04 ` siarhei dot siamashka at gmail dot com
2010-05-09 14:56 ` dougmencken at gmail dot com [this message]
2010-05-17 7:54 ` siarhei dot siamashka at gmail dot com
2010-05-17 9:06 ` siarhei dot siamashka at gmail dot com
2010-05-17 9:08 ` jakub at gcc dot gnu dot org
2010-05-17 10:08 ` siarhei dot siamashka at gmail dot com
2010-05-17 11:31 ` siarhei dot siamashka at gmail dot com
2010-05-17 13:24 ` jakub at gcc dot gnu dot org
2010-05-17 17:20 ` jakub at gcc dot gnu dot org
2010-05-17 17:27 ` jakub at gcc dot gnu dot org
2010-05-17 17:31 ` jakub at gcc dot gnu dot org
2010-05-17 17:34 ` jakub at gcc dot gnu dot org
2010-05-18 10:09 ` siarhei dot siamashka at gmail dot com
2010-05-18 10:59 ` jakub at gcc dot gnu dot org
2010-06-08 14:50 ` siarhei dot siamashka at gmail dot com
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=20100509145648.32050.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).