From: apbianco@gcc.gnu.org
To: apbianco@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
green@cygnus.com, java-prs@gcc.gnu.org, nobody@gcc.gnu.org,
rhug-rhats@sources.redhat.com
Subject: Re: java/4204: java bytecode compilation failure
Date: Thu, 06 Sep 2001 16:23:00 -0000 [thread overview]
Message-ID: <20010906232322.14868.qmail@sourceware.cygnus.com> (raw)
Synopsis: java bytecode compilation failure
Responsible-Changed-From-To: unassigned->apbianco
Responsible-Changed-By: apbianco
Responsible-Changed-When: Thu Sep 6 16:23:22 2001
Responsible-Changed-Why:
Mine
State-Changed-From-To: open->feedback
State-Changed-By: apbianco
State-Changed-When: Thu Sep 6 16:23:22 2001
State-Changed-Why:
A patch exists:
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view&pr=4230&database=gcc
And I verified it fixes the problem.
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view&pr=4204&database=gcc
next reply other threads:[~2001-09-06 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 16:23 apbianco [this message]
2001-09-16 15:09 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=20010906232322.14868.qmail@sourceware.cygnus.com \
--to=apbianco@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=green@cygnus.com \
--cc=java-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
--cc=rhug-rhats@sources.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: 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).