public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Stefaan De Roeck" <stefaandr@hotmail.com>
To: rth@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/5851: tmp-dum.c:2: Internal error: Segmentation fault
Date: Sat, 30 Mar 2002 16:16:00 -0000 [thread overview]
Message-ID: <20020331001601.28735.qmail@sources.redhat.com> (raw)
The following reply was made to PR target/5851; it has been noted by GNATS.
From: "Stefaan De Roeck" <stefaandr@hotmail.com>
To: rth@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, stefaandr@hotmail.com, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: target/5851: tmp-dum.c:2: Internal error: Segmentation fault
Date: Sun, 31 Mar 2002 00:12:55
<html><div style='background-color:'><DIV>May I ask what version of binutils you use? With 2.9.1 I get some kind of "Unknown pseudo-op: '.section'" when assembling _muldi3.o, with the latest release or the cvs I get errors when compiling the assembler for alpha-vms. (I tried gcc-20020325, I hope that's what you meant with 3.1 prerelease...)</DIV>
<DIV> </DIV>
<DIV>Thanks, and sorry for any ignorance, I'm new to this :)</DIV>
<DIV> </DIV>
<DIV>Stefaan</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV></DIV>
<DIV></DIV>>From: rth@gcc.gnu.org
<DIV></DIV>>Reply-To: rth@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rth@gcc.gnu.org, stefaandr@hotmail.com, gcc-gnats@gcc.gnu.org
<DIV></DIV>>To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rth@gcc.gnu.org, stefaandr@hotmail.com
<DIV></DIV>>Subject: Re: target/5851: tmp-dum.c:2: Internal error: Segmentation fault
<DIV></DIV>>Date: 30 Mar 2002 01:21:50 -0000
<DIV></DIV>>Received: from [209.249.29.67] by hotmail.com (3.2) with ESMTP id MHotMailBE6E5FBF005040043221D1F91D430A480; Fri, 29 Mar 2002 17:28:31 -0800
<DIV></DIV>>Received: (qmail 8329 invoked by uid 61); 30 Mar 2002 01:21:50 -0000
<DIV></DIV>>From anonymous@sources.redhat.com Fri, 29 Mar 2002 17:29:09 -0800
<DIV></DIV>>Message-ID: <20020330012150.8328.qmail@sources.redhat.com>
<DIV></DIV>>X-Mailer: gnatsweb 2.9.3
<DIV></DIV>>
<DIV></DIV>>Synopsis: tmp-dum.c:2: Internal error: Segmentation fault
<DIV></DIV>>
<DIV></DIV>>Responsible-Changed-From-To: unassigned->rth
<DIV></DIV>>Responsible-Changed-By: rth
<DIV></DIV>>Responsible-Changed-When: Fri Mar 29 17:21:49 2002
<DIV></DIV>>Responsible-Changed-Why:
<DIV></DIV>> .
<DIV></DIV>>State-Changed-From-To: open->feedback
<DIV></DIV>>State-Changed-By: rth
<DIV></DIV>>State-Changed-When: Fri Mar 29 17:21:49 2002
<DIV></DIV>>State-Changed-Why:
<DIV></DIV>> Can't reproduce with gcc 3.1 prerelease.
<DIV></DIV>>
<DIV></DIV>>http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5851
<DIV></DIV></div><br clear=all><hr>MSN Photos is the easiest way to share and print your photos: <a href='http://g.msn.com/1HM300901/1V'>Click Here</a><br></html>
next reply other threads:[~2002-03-31 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-30 16:16 Stefaan De Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-31 15:44 rth
2002-03-30 16:36 Richard Henderson
2002-03-29 17:21 rth
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=20020331001601.28735.qmail@sources.redhat.com \
--to=stefaandr@hotmail.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=rth@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).