public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: green@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, green@gcc.gnu.org, java-prs@gcc.gnu.org, nobody@gcc.gnu.org, per@bothner.com, rth@redhat.com Subject: Re: java/3087: Re: java eh crash in gcc3 branch Date: Fri, 26 Apr 2002 15:52:00 -0000 [thread overview] Message-ID: <20020426225231.8410.qmail@sources.redhat.com> (raw) Synopsis: Re: java eh crash in gcc3 branch Responsible-Changed-From-To: unassigned->green Responsible-Changed-By: green Responsible-Changed-When: Fri Apr 26 15:52:31 2002 Responsible-Changed-Why: This appears to be fixed in the latest 3.1 branch. State-Changed-From-To: open->feedback State-Changed-By: green State-Changed-When: Fri Apr 26 15:52:31 2002 State-Changed-Why: This appears to be fixed. For some reason the description of the failure has disappeared from this PR. It's still available on the net here: http://gcc.gnu.org/ml/gcc-bugs/2001-06/msg00144.html Can we close? http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3087
next reply other threads:[~2002-04-26 22:52 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-26 15:52 green [this message] 2002-09-17 7:23 green
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=20020426225231.8410.qmail@sources.redhat.com \ --to=green@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=per@bothner.com \ --cc=rth@redhat.com \ /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: linkBe 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).