public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "aph at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/16431] New: Bytecode compiler silently generates incorrect code Date: Thu, 08 Jul 2004 10:19:00 -0000 [thread overview] Message-ID: <20040708101913.16431.aph@gcc.gnu.org> (raw) With some oddly formed class files, the bytecode compiler can spuriously generate additional DECLs for local variable slots, and these DECLs have undefined initial values. This is a regression caused by the tree-SSA merge. The problem arises when there are two different types put onto the stack at different points in the execution. This generates two DECLs, one for each type. Later code that refers to that stack item can do so with a type that is a common superclass of the two types, but we have generated two separate DECLs. The only way properly to fix this is to change the way that stack items are mapped on to DECLs. -- Summary: Bytecode compiler silently generates incorrect code Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: critical Priority: P1 Component: java AssignedTo: aph at gcc dot gnu dot org ReportedBy: aph at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16431
next reply other threads:[~2004-07-08 10:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-08 10:19 aph at gcc dot gnu dot org [this message] 2004-07-08 10:19 ` [Bug java/16431] " aph at gcc dot gnu dot org 2004-07-08 10:25 ` [Bug java/16431] [3.5 Regression] " pinskia at gcc dot gnu dot org 2004-07-21 16:12 ` cvs-commit at gcc dot gnu dot org 2004-07-21 16:13 ` aph at gcc dot gnu dot org 2004-08-09 0: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=20040708101913.16431.aph@gcc.gnu.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: 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).