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/8264: GCC3.2 Illegal Instruction building libgcc2.c
Date: Fri, 09 May 2003 06:46:00 -0000 [thread overview]
Message-ID: <20030509064600.31929.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/8264; it has been noted by GNATS.
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: James Wright <james@jigsawdezign.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/8264: GCC3.2 Illegal Instruction building libgcc2.c
Date: Thu, 8 May 2003 23:41:32 -0700 (PDT)
--- James Wright <james@jigsawdezign.com> wrote:
>
>
> I'm afraid this particular linux box has since
> been replaced, so i'm unable to check...
No problem. Since there are a number of successful 3.2
reports on i586-pc-linux-gnu. I guess we'll close this
bug.
Dara
>
>
> Sorry,
> James
>
>
>
> On Wed, 7 May 2003 22:11:45 -0700
> Dara Hazeghi <dhazeghi@yahoo.com> wrote:
>
> >
>
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
>
> > trail&database=gcc&pr=8264
> >
> > Hello,
> >
> > could the submitter of this report check whether
> this issue is still
> > present in gcc 3.2.3, or send the preprocessed
> source that is crashing
> > the build (as the error message mentions). Thanks,
> >
> > Dara
> >
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
next reply other threads:[~2003-05-09 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 6:46 Dara Hazeghi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 15:36 bangerth
2003-05-08 10:40 giovannibajo
2003-05-08 5:16 Dara Hazeghi
2002-10-17 13:06 james
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=20030509064600.31929.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).