From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12590 invoked by alias); 17 Feb 2005 23:49:16 -0000 Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org Received: (qmail 12567 invoked by uid 48); 17 Feb 2005 23:49:15 -0000 Date: Fri, 18 Feb 2005 00:01:00 -0000 From: "bonniot at users dot sf dot net" To: java-prs@gcc.gnu.org Message-ID: <20050217234912.20044.bonniot@users.sf.net> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug java/20044] New: Wrong method call semantics (maybe instanceof/invokespecial) X-Bugzilla-Reason: CC X-SW-Source: 2005-q1/txt/msg00424.txt.bz2 List-Id: This is a very small testcase, in which the code generated by gcj does not behave correctly at runtime. I set the severity as critical because there is no notification that something went wrong while the wrong method gets called, and I see no workaround. I suppose that there is a problem either with an instanceof test, or with the implementation of invokespecial. Feel free to update the summary if this turns out to be the wrong intuitition. Attached are three small bytecode classes (I could not reproduce the bug from Java sources). # Normal behaviour, using Sun's JDK $ java test.fun true $ gcj --main=test.fun test/*.class $ ./a.out false Tested with gcj 4.0.0 20050212. -- Summary: Wrong method call semantics (maybe instanceof/invokespecial) Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: critical Priority: P2 Component: java AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: bonniot at users dot sf dot net CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org GCC host triplet: i386-debian-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20044