public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: egcs@cygnus.com
Subject: latest snapshot won't bootstrap on mips-sgi-irix5.2
Date: Wed, 20 May 1998 04:58:00 -0000	[thread overview]
Message-ID: <ord8d9fg0h.fsf@zecarneiro.lsd.dcc.unicamp.br> (raw)

I've got a repeatable bootstrap failure on mips-sgi-irix5.2 with
BOOT_CFLAGS="-O4 -g", configured with haifa scheduler disabled, but
shared libraries enabled.  The problem occurs while building stage2
libgcc.a (i.e., ./xgcc was built with stage1/xgcc).  Here's the actual 
error:

./xgcc -B./ -O2   -DIN_GCC    -W -Wall -O4 -g -I./include   -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -fexceptions   -I. -I/n/temp1/gcctest/bin/../src/egcs/gcc -I/n/temp1/gcctest/bin/../src/egcs/gcc/config \
  -c -fexceptions /n/temp1/gcctest/bin/../src/egcs/gcc/cp/exception.cc
/n/temp1/gcctest/bin/../src/egcs/gcc/cp/exception.cc:312: Internal compiler error.
/n/temp1/gcctest/bin/../src/egcs/gcc/cp/exception.cc:312: Please submit a full bug report to `egcs-bugs@cygnus.com'.

The stack trace follows:

#0  0xf9716e0 in _lfree () at malloc.c:869
#1  0xf9709d4 in _free () at malloc.c:337
#2  0xfacc370 in fclose () at flush.c:61
#3  0x4a6064 in finish_parse ()
    at /n/temp1/gcctest/bin/../src/egcs/gcc/cp/lex.c:907
#4  0x506130 in compile_file (name=0x4e <Address 0x4e out of bounds>)
    at /n/temp1/gcctest/bin/../src/egcs/gcc/toplev.c:2812
#5  0x5117a8 in main (argc=16, argv=0x7fffaea4, envp=0xe)
    at /n/temp1/gcctest/bin/../src/egcs/gcc/toplev.c:4354

-- 
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil


                 reply	other threads:[~1998-05-20  4:58 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=ord8d9fg0h.fsf@zecarneiro.lsd.dcc.unicamp.br \
    --to=oliva@dcc.unicamp.br \
    --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).