public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsturm at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug java/12739] New: gcj emits dead bytecode Date: Thu, 23 Oct 2003 03:28:00 -0000 [thread overview] Message-ID: <20031023032624.12739.jsturm@gcc.gnu.org> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12739 Summary: gcj emits dead bytecode Product: gcc Version: 3.4 Status: UNCONFIRMED Severity: normal Priority: P2 Component: java AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jsturm at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org For the test case: class T { int t() { try { return 0; } finally { } } } Compare the bytecode created with 3.2.2: Method name:"t" Signature: 6=()int Attribute "Code", length:26, max_stack:1, max_locals:1, code_length:2 0: iconst_0 1: ireturn vs. current CVS: Method name:"t" Signature: 6=()int Attribute "Code", length:48, max_stack:2, max_locals:4, code_length:16 0: iconst_0 1: istore_1 2: jsr 13 5: iload_1 6: ireturn 7: astore_3 8: jsr 13 11: aload_3 12: athrow 13: astore_2 14: ret 2 Exceptions (count: 1): start: 0, end: 7, handler: 7, type: 0 /* finally */ Probably caused by: 2003-09-03 Jeff Sturm <jsturm@one-point.com> * parse.y: Include cgraph.h. (block): Don't special-case empty block production.
next reply other threads:[~2003-10-23 3:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-23 3:28 jsturm at gcc dot gnu dot org [this message] 2003-10-23 3:31 ` [Bug java/12739] " jsturm at gcc dot gnu dot org 2003-10-23 3:33 ` [Bug java/12739] [3.4 Regression] " pinskia at gcc dot gnu dot org 2003-10-23 3:35 ` pinskia at gcc dot gnu dot org 2003-10-27 18:08 ` jsturm at gcc dot gnu dot org 2003-11-18 3:42 ` cvs-commit at gcc dot gnu dot org 2003-11-18 3:53 ` jsturm 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=20031023032624.12739.jsturm@gcc.gnu.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).