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 17:56:00 -0000 [thread overview]
Message-ID: <20030225175600.17993.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@gw.mipt.sw.ru
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Subject: Re: bootstrap/9845: [Alpha-ev6] libgcc2.c:956: internal compiler error: Segmentation fault
Date: 25 Feb 2003 18:47:59 +0100
malfet@gw.mipt.sw.ru writes:
> > 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?
>
> I downloaded gcc from cvs, run ./configure and then make.
> Processor is 2164, distribution is RedHat Linux 6.0 for Alpha, gcc is 2.91.66
> nik@blackbox nik]$ gcc -v
> Reading specs from /usr/lib/gcc-lib/alpha-redhat-linux/egcs-2.91.66/specs
> gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
> This error occures with all cvs snapshots from 17 Feb up to this
> day. May be the problem is that I have alphaev6, but everything is
> compiled for alpha-ev67?
Are you sure you don't have an ev67? What does grep model
/proc/cpuinfo say? In any case, this shouldn't be the reason. The only
thing I can currently think of is that 2.91.66 miscompiles xgcc. Could
you maybe try installing, say, gcc 3.2, and bootstrap with that?
--
Falk
next reply other threads:[~2003-02-25 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 17:56 Falk Hueffner [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-17 23:28 bangerth
2003-02-25 13:26 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=20030225175600.17993.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).