From: Brad Reick <bgreick@gauss.cord.edu>
To: egcs@cygnus.com
Subject: Boostrap failure 19981101 on powerpc
Date: Fri, 06 Nov 1998 08:30:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.981105143235.13924D-100000@gauss.cord.edu> (raw)
In-Reply-To: <19981104221536.D27313@dgii.com>
I have been trying to compile recent snapshots and they all seem to fail
on during the stage1 build, on the same piece of code, regmove.c. In
fact I havent had any success since I built egcs 1.0.3 months ago. Were
there some major changes to regmove.c that would break the build on the
ppc or could something else be at work here?
System info:
target: powerpc-unknown-linux-gnulibc1 (mklinux)
binutils 2.9.1
egcs 1.0.3
Here are the errors encountered on the most recent build attempt:
stage1/xgcc -Bstage1/ -B/users/local//powerpc-unknown-linux-gnulibc1/bin/
-c -DIN_GCC -DUSE_GNULIBC_1 -W -Wall -O2 -g -O2 -DHAVE_CONFIG_H
-DHAIFA -I. -I. -I./config -I./../include regmove.c
regmove.c: In function `regmove_optimize':
regmove.c:196: warning: array subscript has type `char'
regmove.c:210: warning: array subscript has type `char'
regmove.c:162: warning: unused variable `matching_operand'
regmove.c:161: warning: unused variable `output_operand'
regmove.c:622: warning: suggest parentheses around assignment used as
truth value
regmove.c:762: warning: array subscript has type `char'
regmove.c:776: warning: array subscript has type `char'
regmove.c:728: warning: unused variable `matching_operand'
regmove.c:727: warning: unused variable `output_operand'
regmove.c:933: warning: suggest parentheses around assignment used as
truth value
regmove.c:116: warning: unused parameter `nregs'
regmove.c:234: warning: `dst_note' might be used uninitialized in this
function
regmove.c:238: warning: `insn_const' might be used uninitialized in this
function
regmove.c:238: warning: `newconst' might be used uninitialized in this
function
regmove.c:363: warning: `set2' might be used uninitialized in this function
regmove.c:542: warning: `set2' might be used uninitialized in this function
xgcc: Internal compiler error: program cc1 got fatal signal 11
make[2]: *** [regmove.o] Error 1
make[2]: Leaving directory `/users/tools/egcs-19981101/gcc'
make[1]: *** [bootstrap] Error 2
Cheers,
Bradley Reick
bgreick@gauss.cord.edu
next prev parent reply other threads:[~1998-11-06 8:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-18 21:00 libiberty configure fails on svr4/svr5 native Robert Lipe
1998-11-04 20:47 ` Joern Rennecke
1998-11-04 20:47 ` Robert Lipe
1998-11-04 20:47 ` Joern Rennecke
1998-11-05 5:01 ` Ben Elliston
1999-01-31 23:58 ` Ben Elliston
1998-11-06 8:30 ` Brad Reick [this message]
1998-11-06 4:27 ` Andreas Schwab
1998-11-09 21:55 ` Joern Rennecke
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=Pine.SOL.3.91.981105143235.13924D-100000@gauss.cord.edu \
--to=bgreick@gauss.cord.edu \
--cc=egcs@cygnus.com \
/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).