From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: gcc@gcc.gnu.org
Subject: Solaris 8/SPARC bootstrap broken building 64-bit libgcc
Date: Fri, 04 Jul 2003 12:53:00 -0000 [thread overview]
Message-ID: <16133.30814.486754.373909@xayide.TechFak.Uni-Bielefeld.DE> (raw)
Current mainline fails to bootstrap on bi-arch sparc-sun-solaris2.8:
/vol/gcc/obj/gcc-3.4-20030704/8-gcc/gcc/xgcc -B/vol/gcc/obj/gcc-3.4-20030704/8-gcc/gcc/ -B/vol/gcc/share/sparc-sun-solaris2.8/bin/ -B/vol/gcc/share/sparc-sun-solaris2.8/lib/ -isystem /vol/gcc/share/sparc-sun-solaris2.8/include -isystem /vol/gcc/share/sparc-sun-solaris2.8/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/vol/gnu/src/gcc/gcc-dist/gcc -I/vol/gnu/src/gcc/gcc-dist/gcc/. -I/vol/gnu/src/gcc/gcc-dist/gcc/config -I/vol/gnu/src/gcc/gcc-dist/gcc/../include -m64 -DL__gcc_bcmp -c /vol/gnu/src/gcc/gcc-dist/gcc/libgcc2.c -o libgcc/sparcv9/__gcc_bcmp.o
/vol/gcc/obj/gcc-3.4-20030704/8-gcc/gcc/xgcc -B/vol/gcc/obj/gcc-3.4-20030704/8-gcc/gcc/ -B/vol/gcc/share/sparc-sun-solaris2.8/bin/ -B/vol/gcc/share/sparc-sun-solaris2.8/lib/ -isystem /vol/gcc/share/sparc-sun-solaris2.8/include -isystem /vol/gcc/share/sparc-sun-solaris2.8/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/vol/gnu/src/gcc/gcc-dist/gcc -I/vol/gnu/src/gcc/gcc-dist/gcc/. -I/vol/gnu/src/gcc/gcc-dist/gcc/config -I/vol/gnu/src/gcc/gcc-dist/gcc/../include -m64 -DL_gcov -c /vol/gnu/src/gcc/gcc-dist/gcc/libgcov.c -o libgcc/sparcv9/_gcov.o
/vol/gnu/src/gcc/gcc-dist/gcc/libgcc2.c: In function `__gcc_bcmp':
/vol/gnu/src/gcc/gcc-dist/gcc/libgcc2.c:1519: error: head insn 102 for block 0 not found in the insn stream
/vol/gnu/src/gcc/gcc-dist/gcc/libgcc2.c:1519: internal compiler error: Segmentation Fault
The current state of mainline gets increasingly annoying: it's almost
impossible to get any work done when at any random time at least one of
your platforms doesn't bootstrap at all, while more often than not most of
them don't. I spend more time tracking down the culprit patches than
anything else ;-(
Rainer
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
next reply other threads:[~2003-07-04 12:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-04 12:53 Rainer Orth [this message]
2003-07-04 13:22 ` Andrew Pinski
2003-07-04 21:12 ` Phil Edwards
2003-07-04 22:53 ` Eric Botcazou
2003-07-04 23:07 ` Phil Edwards
2003-07-05 8:37 ` Eric Botcazou
2003-07-06 22:22 ` Gerald Pfeifer
2003-07-06 22:47 ` Phil Edwards
2003-07-06 23:40 ` Eric Botcazou
2003-07-12 16:14 ` Eric Botcazou
2003-07-07 2:59 ` Jeff Sturm
2003-07-07 12:50 ` Gerald Pfeifer
2003-07-07 14:41 ` Mark Mitchell
[not found] ` <Pine.BSF.4.56.0307090031480.86235@acrux.dbai.tuwien.ac.at>
[not found] ` <16139.18358.209462.246169@xayide.TechFak.Uni-Bielefeld.DE>
2003-07-14 16:30 ` Release criteria (was: PATCH for Re: Solaris 8/SPARC bootstrap broken building 64-bit libgcc) Gerald Pfeifer
2003-07-17 18:12 ` Mark Mitchell
2003-07-14 21:39 ` Solaris 8/SPARC bootstrap broken building 64-bit libgcc Phil Edwards
2003-07-14 22:47 ` Eric Botcazou
2003-07-14 22:49 ` Phil Edwards
2003-07-14 23:43 ` Eric Botcazou
2003-07-15 0:45 ` Phil Edwards
2003-07-15 7:47 ` Eric Botcazou
2003-07-16 20:22 ` Phil Edwards
2003-07-16 20:29 ` Eric Botcazou
2003-07-16 20:30 ` Phil Edwards
2003-07-16 20:38 ` Eric Botcazou
2003-07-05 5:13 ` Andreas Jaeger
2003-07-04 23:03 John David Anglin
[not found] <no.id>
2003-07-05 17:01 ` John David Anglin
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=16133.30814.486754.373909@xayide.TechFak.Uni-Bielefeld.DE \
--to=ro@techfak.uni-bielefeld.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).