public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: mitchell@manly.delconet.com
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/6560: Compiler fails to build
Date: Sat, 04 May 2002 20:06:00 -0000	[thread overview]
Message-ID: <20020505030235.12964.qmail@sources.redhat.com> (raw)


>Number:         6560
>Category:       bootstrap
>Synopsis:       Compiler fails to build
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 04 20:06:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     MIIM site maintainer
>Release:        2.95
>Organization:
>Environment:
DEC-VAX-ULTRIX4.3 -- Digital Equipment VAX, Ultrix 4.3
>Description:
On a VAX running Ultrix, with GCC 2.7.2.3 installed,
attempting to build GCC 2.9.5 produces the following
error during the build:

<14 hours of preceding build text deleted>
touch stmp-fixproto
if [ -f libgcc2.ready ] ; then          true;  else     touch libgcc2.ready;  fi
case " c proto gcov CHILL c++ f77 java objc " in  *" "[cC]"++ "*)    echo tinfo.o tinfo2.o new.o opnew.o
opnewnt.o opvnew.o opvnewnt.o  opdel.o opdelnt.o opvdel.o opvdelnt.o exception.o > cplib2.new;;  *)    ec
ho "" > cplib2.new;;  esac
mv -f cplib2.new cplib2.txt
rm -f tmplibgcc2.a
for name in _muldi3 _divdi3 _moddi3 _udivdi3 _umoddi3 _negdi2  _lshrdi3 _ashldi3 _ashrdi3 _ffsdi2  _udiv_
w_sdiv _udivmoddi4 _cmpdi2 _ucmpdi2 _floatdidf _floatdisf  _fixunsdfsi _fixunssfsi _fixunsdfdi _fixdfdi _
fixunssfdi _fixsfdi  _fixxfdi _fixunsxfdi _floatdixf _fixunsxfsi  _fixtfdi _fixunstfdi _floatditf  __gcc_
bcmp _varargs __dummy _eprintf  _bb _shtab _clear_cache _trampoline __main _exit  _ctors _pure;  do    ec
ho ${name};    /usr/local/gcc-2.95/gcc/xgcc -B/usr/local/gcc-2.95/gcc/ -B/usr/local/vax-dec-ultrix4.3/bin
/ -I/usr/local/vax-dec-ultrix4.3/include -O2   -DIN_GCC     -g -O2 -I./include   -g1  -DIN_LIBGCC2 -D__GC
C_FLOAT_NOT_NEEDED   -I. -I. -I./config -I./../include -c -DL${name}        -DUSE_COLLECT2 ./libgcc2.c -o
 ${name}.o;    if [ $? -eq 0 ] ; then true; else exit 1; fi;    ar rc tmplibgcc2.a ${name}.o;    rm -f ${
name}.o;  done
_muldi3
_divdi3
_moddi3
_udivdi3
_umoddi3
_negdi2
_lshrdi3
_ashldi3
_ashrdi3
_ffsdi2
_udiv_w_sdiv
_udivmoddi4
_cmpdi2
_ucmpdi2
_floatdidf
_floatdisf
_fixunsdfsi
_fixunssfsi
_fixunsdfdi
_fixdfdi
_fixunssfdi
_fixsfdi
_fixxfdi
_fixunsxfdi
_floatdixf
_fixunsxfsi
_fixtfdi
_fixunstfdi
_floatditf
__gcc_bcmp
_varargs
./libgcc2.c: In function `__builtin_saveregs':
./libgcc2.c:1396: Internal compiler error in `emit_call_1', at calls.c:446
Please submit a full bug report.
See <URL:http://egcs.cygnus.com/faq.html#bugreport> for instructions.
*** Error code 1
 
Stop.
*** Error code 1
 
Stop.
#
>How-To-Repeat:
Start the build over again and wait 14 hours.
>Fix:
Unknown
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-05-05  3:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020505030235.12964.qmail@sources.redhat.com \
    --to=mitchell@manly.delconet.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).