public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug java/4811] Incorrect error accessing non-existant outer field Date: Tue, 09 Jan 2007 20:45:00 -0000 [thread overview] Message-ID: <20070109204347.14477.qmail@sourceware.org> (raw) In-Reply-To: <bug-4811-6651@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from tromey at gcc dot gnu dot org 2007-01-09 20:43 ------- All gcj front end bugs have been fixed by the gcj-eclipse branch merge. I'm mass-closing the affected PRs. If you believe one of these was closed in error, please reopen it with a note explaining why. Thanks. -- tromey at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=4811
next parent reply other threads:[~2007-01-09 20:45 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-4811-6651@http.gcc.gnu.org/bugzilla/> 2007-01-09 20:45 ` tromey at gcc dot gnu dot org [this message] [not found] <20011106185601.4811.bryce@mckinlay.net.nz> 2003-08-17 20:43 ` pinskia at gcc dot gnu dot org 2004-01-07 20:01 ` pinskia at gcc dot gnu dot org 2003-05-22 17:16 aph@gcc.gnu.org
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=20070109204347.14477.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: 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).