public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/9899: bootstrap failed on stage3 build
Date: Fri, 16 May 2003 18:36:00 -0000	[thread overview]
Message-ID: <20030516183601.18248.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/9899; it has been noted by GNATS.

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: Oleksiy Melnyk <O.Melnyk@upc.kiev.ua>
Cc: gcc-gnats@gcc.gnu.org, roger@www.eyesopen.com
Subject: Re: bootstrap/9899: bootstrap failed on stage3 build
Date: Fri, 16 May 2003 11:27:08 -0700 (PDT)

 --- Oleksiy Melnyk <O.Melnyk@upc.kiev.ua> wrote:
 > Unfortunatelly I can't check _that_ error - another
 > one on the way:-(.
 > Should I report that bug, or wait for a newer OS
 > version(I'll got one next month)?
 
 Well, ideally we'd like to fix this problem on this
 platform... Roger, does this look familiar to you by
 any chance? Thanks,
 
 Dara
 > 
 > ...
 > stage1/xgcc -Bstage1/
 > -B/usr/local/alphaev68-dec-osf5.0/bin/ -g -O2
 > -DIN_GCC 
 >   -W -Wall -Wwrite-strings -Wstrict-prototypes
 > -Wmissing-prototypes 
 > -Wtraditional -pedantic -Wno-long-long  
 > -DHAVE_CONFIG_H -DGENERATOR_FILE  -o 
 > genattrtab genattrtab.o genautomata.o rtl.o
 > read-rtl.o bitmap.o ggc-none.o 
 > gensupport.o insn-conditions.o print-rtl1.o errors.o
 > varray.o 
 > ../libiberty/libiberty.a -lm
 > 
 > ./genattrtab ../../gcc-3.3/gcc/config/alpha/alpha.md
 > > tmp-attrtab.c
 > Check description...genattrtab: Internal error:
 > /bin/sh: 512435 Memory fault - 
 > core dumped
 > make[2]: *** [s-attrtab] Error 139
 > make[2]: Leaving directory
 > `/usr/local/src/gcc-build/gcc'
 > make[1]: *** [stage2_build] Error 2
 > make[1]: Leaving directory
 > `/usr/local/src/gcc-build/gcc'
 > make: *** [bootstrap] Error 2
 > 
 > $ dbx genattrtab core
 > dbx version 5.0
 > Type 'help' for help.
 > Core file created by program "genattrtab"
 > 
 > signal Segmentation fault at >*[strlen,
 > 0x3ff801bbd80]  ldq_u   t0, 0(a0)
 > (dbx) tstack
 > 
 > Thread 0x3:
 >  >  0 strlen(0x14000ce28, 0x1400002c0, 0x0,
 > 0x1400181f8, 0x3ffc0087f80) 
 > [0x3ff801bbd80]
 >     1 _doprnt_dis(0x14000a4c3, 0x10000001c,
 > 0x11fffbec0, 0x10, 0x0) 
 > [0x3ff801bf298]
 >     2 _doprnt(0x0, 0x14009d680, 0x3ff8015a26c,
 > 0x11fffbf50, 0x100000008) 
 > [0x3ff800d3690]
 >     3 vfprintf(0x11fffbf50, 0x100000008,
 > 0x14000a4c3, 0x3ffc0089c70, 0x0) 
 > [0x3ff8015a268]
 >     4 internal_error()
 > ["../../gcc-3.3/gcc/errors.c":6, 0x12002e78c]
 >     5 fancy_abort() ["../../gcc-3.3/gcc/errors.c":6,
 > 0x12002e898]
 >     6 evaluate_max_reserv_cycles()
 > ["../../gcc-3.3/gcc/genautomata.c":6, 
 > 0x120016364]
 >     7 main() ["../../gcc-3.3/gcc/genattrtab.c":6,
 > 0x1200120cc]
 
 
 __________________________________
 Do you Yahoo!?
 The New Yahoo! Search - Faster. Easier. Bingo.
 http://search.yahoo.com


             reply	other threads:[~2003-05-16 18:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 18:36 Dara Hazeghi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 19:16 Dara Hazeghi
2003-03-02  3:06 A.Melnik

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=20030516183601.18248.qmail@sources.redhat.com \
    --to=dhazeghi@yahoo.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).