From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32285 invoked by alias); 22 Feb 2005 15:06:00 -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 32264 invoked by uid 48); 22 Feb 2005 15:05:59 -0000 Date: Tue, 22 Feb 2005 15:25:00 -0000 Message-ID: <20050222150559.32263.qmail@sourceware.org> From: "aph at gcc dot gnu dot org" To: java-prs@gcc.gnu.org In-Reply-To: <20050220150755.20104.overholt@redhat.com> References: <20050220150755.20104.overholt@redhat.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug java/20104] gij fails on ppc and not on x86 X-Bugzilla-Reason: CC X-SW-Source: 2005-q1/txt/msg00480.txt.bz2 List-Id: ------- Additional Comments From aph at gcc dot gnu dot org 2005-02-22 15:05 ------- The failure is here: package org.eclipse.jdt.internal.compiler.impl; public class CompilerOptions ... { void updateSeverity(long irritant, Object severityString) { if (ERROR.equals(severityString)) { this.errorThreshold |= irritant; and the corresponding bytecode is: Method name:"updateSeverity" Signature: (long,java.lang.Object)void Attribute "Code", length:208, max_stack:7, max_locals:4, code_length:110 0: ldc 2: aload_3 3: invokevirtual The aload_3 looks wrong to me. So, there are two separate issues: 1. Why was aload_3 generated? Which compiler genrated it? 2. How did this get past the libgcj verifier? tromey added to CC list to investigate the verifier. overholt, please let me know how this jar file was generated. Bug upgraded to critical. -- What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |critical Status|UNCONFIRMED |NEW Ever Confirmed| |1 Last reconfirmed|0000-00-00 00:00:00 |2005-02-22 15:05:57 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20104