From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2137 invoked by alias); 21 Apr 2005 09:05:24 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 2008 invoked by uid 48); 21 Apr 2005 09:05:17 -0000 Date: Thu, 21 Apr 2005 09:05:00 -0000 Message-ID: <20050421090517.2005.qmail@sourceware.org> From: "bothner at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050304081857.20312.davidw@dedasys.com> References: <20050304081857.20312.davidw@dedasys.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug java/20312] No warning on bad method X-Bugzilla-Reason: CC X-SW-Source: 2005-04/txt/msg03001.txt.bz2 List-Id: ------- 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