public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/9845: [Alpha-ev6] libgcc2.c:956: internal compiler error: Segmentation fault
Date: Tue, 25 Feb 2003 13:26:00 -0000 [thread overview]
Message-ID: <20030225132600.12402.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/9845; it has been noted by GNATS.
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: malfet@mipt.sw.ru
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/9845: [Alpha-ev6] libgcc2.c:956: internal compiler error: Segmentation fault
Date: 25 Feb 2003 14:16:26 +0100
malfet@mipt.sw.ru writes:
> >Number: 9845
> >Category: bootstrap
> >Synopsis: [Alpha-ev6] libgcc2.c:956: internal compiler error: Segmentation fault
> >Release: GCC-CVS-25.02.03
>
> >Description:
> Full command line is follows:
> ./xgcc -B./ -B/usr/local/alphaev67-unknown-linux-gnu/bin/ -isystem /usr/local/alphaev67-unknown-linux-gnu/include -isystem /usr/local/alphaev67-unknown-linux-gnu/sys-include -L/root/gcc-cvs-25.02.03/gcc/../ld -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -mieee -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I. -I./. -I./config -I./../include -DL_divdi3 -c ./libgcc2.c -fexceptions -fnon-call-exceptions -o libgcc/./_div di3.o
> Output:
> libgcc2.c: In function `__divti3':
> libgcc2.c:956: internal compiler error: Segmentation fault
I cannot reproduce this on alphaev68-unknown-linux-gnu. Could you
please tell the exact command line you used to compile (bootstrap or
not?), and the compiler you used for stage 1?
--
Falk
next reply other threads:[~2003-02-25 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 13:26 Falk Hueffner [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-17 23:28 bangerth
2003-02-25 17:56 Falk Hueffner
2003-02-25 9:56 malfet
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=20030225132600.12402.qmail@sources.redhat.com \
--to=falk.hueffner@student.uni-tuebingen.de \
--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).