public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aph at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug java/20104] gij fails on ppc and not on x86 Date: Tue, 22 Feb 2005 20:02:00 -0000 [thread overview] Message-ID: <20050222150559.32257.qmail@sourceware.org> (raw) In-Reply-To: <20050220150755.20104.overholt@redhat.com> ------- 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 <String "error"> 2: aload_3 3: invokevirtual <Method java.lang.String.equals (java.lang.Object)boolean> 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
next prev parent reply other threads:[~2005-02-22 15:06 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-20 19:45 [Bug java/20104] New: " overholt at redhat dot com 2005-02-20 19:57 ` [Bug java/20104] " overholt at redhat dot com 2005-02-20 20:14 ` pinskia at gcc dot gnu dot org 2005-02-22 19:58 ` aph at gcc dot gnu dot org 2005-02-22 20:02 ` aph at gcc dot gnu dot org [this message] 2005-02-22 20:07 ` overholt at redhat dot com 2005-02-22 20:22 ` overholt at redhat dot com 2005-02-22 20:22 ` aph at gcc dot gnu dot org 2005-02-22 21:55 ` aph at gcc dot gnu dot org 2005-02-23 5:32 ` andreast at gcc dot gnu dot org 2005-02-23 17:10 ` [Bug libffi/20104] " cvs-commit at gcc dot gnu dot org 2005-02-23 17:16 ` cvs-commit at gcc dot gnu dot org 2005-02-23 17:19 ` [Bug libgcj/20104] " aph at gcc dot gnu dot org 2005-02-25 1:21 ` [Bug libffi/20104] " overholt at redhat dot com 2005-04-20 2:36 ` pinskia 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=20050222150559.32257.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).