public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Christian Jönsson" <christian@j-son.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/7995: ICE in gcc cvs trunk 20020921 when compiling libstdc++-v3/src/complex_io.cc on sparc64-linux
Date: Mon, 23 Sep 2002 03:46:00 -0000 [thread overview]
Message-ID: <20020923104603.911.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/7995; it has been noted by GNATS.
From: =?iso-8859-1?Q?Christian_J=F6nsson?= <christian@j-son.org>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Cc:
Subject: Re: libstdc++/7995: ICE in gcc cvs trunk 20020921 when compiling libstdc++-v3/src/complex_io.cc on sparc64-linux
Date: Mon, 23 Sep 2002 12:42:01 +0200
On Sat, Sep 21, 2002 at 01:36:01PM -0000, gcc-gnats@gcc.gnu.org wrote:
> Thank you very much for your problem report.
> It has the internal identification `libstdc++/7995'.
> The individual assigned to look at your
> report is: unassigned.
>
> >Category: libstdc++
> >Responsible: unassigned
> >Synopsis: ICE in gcc cvs trunk 20020921 when compiling libstdc++-v3/src/complex_io.cc on sparc64-linux
> >Arrival-Date: Sat Sep 21 06:36:01 PDT 2002
The problem still exists (LAST_UPDATED: Mon Sep 23 05:42:04 UTC 2002)
and is as far as I can tell the same problem as reported in
http://gcc.gnu.org/ml/gcc-testresults/2002-09/msg00768.html
Cheers,
/ChJ
next reply other threads:[~2002-09-23 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 3:46 Christian Jönsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-03 6:12 davem
2002-10-03 1:16 David S. Miller
2002-10-03 1:08 davem
2002-10-02 23:36 Christian Jönsson
2002-10-02 16:56 David S. Miller
2002-10-02 16:49 davem
2002-10-02 8:16 Christian Jönsson
2002-10-01 20:56 davem
2002-09-25 23:56 Christian Jönsson
2002-09-21 6:36 christian
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=20020923104603.911.qmail@sources.redhat.com \
--to=christian@j-son.org \
--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).