public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "bothner at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/20312] No warning on bad method
Date: Thu, 21 Apr 2005 09:05:00 -0000	[thread overview]
Message-ID: <20050421090518.2012.qmail@sourceware.org> (raw)
In-Reply-To: <20050304081857.20312.davidw@dedasys.com>


------- Additional Comments From bothner at gcc dot gnu dot org  2005-04-21 09:05 -------
This patch can cause an ICE when the super-class is byte-compiled.
If a byte-compiled method M in a super-class throws exception X,
we try to emit an erroneous error message that M can't throw X
(because we don't analyze the bytecode).  Worse, because M
doesn't have DECL_FUNCTION_WFL set, we get an ICE in parse_error_context.

The problem is check_interface_throws_clauses, which seems to be doing way
too much work ... it should be not be checking that
"The exception must be a subclass of an exception thrown" in super-classes.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20312


  parent reply	other threads:[~2005-04-21  9:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 15:33 [Bug java/20312] New: " davidw at dedasys dot com
2005-03-05 16:33 ` [Bug java/20312] " pinskia at gcc dot gnu dot org
2005-03-11  7:29 ` rmathew at gcc dot gnu dot org
2005-03-11  9:16 ` cvs-commit at gcc dot gnu dot org
2005-03-12  5:36 ` pinskia at gcc dot gnu dot org
2005-04-21  9:05 ` bothner at gcc dot gnu dot org [this message]
2005-07-21  0:28 ` pinskia at gcc dot gnu dot org
     [not found] <bug-20312-10209@http.gcc.gnu.org/bugzilla/>
2007-01-30  1:53 ` daney at gcc dot gnu dot 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=20050421090518.2012.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).