public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
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 (fwd)
Date: Mon, 17 Mar 2003 23:36:00 -0000 [thread overview]
Message-ID: <20030317233601.23378.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/9845; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: bootstrap/9845: [Alpha-ev6] libgcc2.c:956: internal compiler
error: Segmentation fault (fwd)
Date: Mon, 17 Mar 2003 17:27:59 -0600 (CST)
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.
--=-=-=
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0303171727282.26889@gandalf.ticam.utexas.edu>
---------- Forwarded message ----------
Date: 16 Mar 2003 14:42:50 +0100
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: bangerth@dealii.org
Subject: [Nikita Shulga <malfet@jscc.ru>] Re: bootstrap/9845: [Alpha-ev6]
libgcc2.c:956: internal compiler error: Segmentation fault
Hallo,
Laut Submitter ist das Problem inzwischen verschwunden, koenntest du
vielleicht den Report schliessen?
Gruss,
Falk
--=-=-=
Content-Type: MESSAGE/RFC822; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0303171727283.26889@gandalf.ticam.utexas.edu>
Content-Description:
Content-Disposition: INLINE
X-From-Line: malfet@jscc.ru Wed Feb 26 13:14:34 2003
Return-Path: <malfet@jscc.ru>
Received: from mx01.uni-tuebingen.de (mx01.uni-tuebingen.de [192.168.3.11])
by mailserv05.uni-tuebingen.de (8.12.3/8.12.3) with ESMTP id h1QADors023658
for <zxmjz18@mailserv05.uni-tuebingen.de>; Wed, 26 Feb 2003 11:13:50 +0100
Received: from mtu-net.ru (venezuela.mtu.ru [195.34.32.76])
by mx01.uni-tuebingen.de (8.12.3/8.12.3) with ESMTP id h1QADmPU020099
for <falk.hueffner@student.uni-tuebingen.de>; Wed, 26 Feb 2003 11:13:49 +0100
Received: from [213.147.59.149] (HELO bertha.local)
by mtu-net.ru (CommuniGate Pro SMTP 4.0.6)
with ESMTP id 57943714 for falk.hueffner@student.uni-tuebingen.de; Wed, 26 Feb 2003 13:12:03 +0300
From: Nikita Shulga <malfet@jscc.ru>
To: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
Subject: Re: bootstrap/9845: [Alpha-ev6] libgcc2.c:956: internal compiler error: Segmentation fault
Date: Wed, 26 Feb 2003 13:14:34 +0300
User-Agent: KMail/1.5.9
References: <20030225094819.10726.qmail@sources.redhat.com> <20030225224633.A26717@srv.mipt.sw.ru> <87isv8fazt.fsf@student.uni-tuebingen.de>
In-Reply-To: <87isv8fazt.fsf@student.uni-tuebingen.de>
Content-Disposition: inline
Message-Id: <200302261314.34820.malfet@jscc.ru>
X-AntiVirus: checked by AntiVir Milter 1.0.0.8; AVE 6.18.0.2; VDF 6.18.0.9
Status:
X-Content-Length: 273
X-Spam-Status: No, hits=-4.7 required=5.0
tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,
USER_AGENT,USER_AGENT_KMAIL version=2.44
X-Spam-Level:
Lines: 7
Xref: juist private-2003-02:156
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
> Well, I don't know where to get it for Red Hat... You could try to
> compile it yourself from the sources at gcc.gnu.org.
Thanks a lot! This helps. I compile gcc-3.2.2 with egcs-2.91, and after then
internal compiler error in gcc-cvs disappears.
Lots of thanks,
Nikita
--=-=-=
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0303171727284.26889@gandalf.ticam.utexas.edu>
Content-Description:
--
Falk
--=-=-=--
reply other threads:[~2003-03-17 23:36 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=20030317233601.23378.qmail@sources.redhat.com \
--to=bangerth@ticam.utexas.edu \
--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).