public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug java/38827] New: gcj emitting incorrect code Date: Tue, 13 Jan 2009 16:03:00 -0000 [thread overview] Message-ID: <bug-38827-16947@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 2022 bytes --] I originally found this problem when trying to compile a Java package written by the Universität Stuttgart's institute IKR. I was using Debian's gcj package, version 4.3.2-2, but can likewise reproduce this using SVN trunk, as well as Debian's 4.2.4-4 package. I completely reduced the test case to the following: public class Bug_Class { } public interface Bug_Interface { } public class Bug { public <X extends Bug_Class & Bug_Interface> Bug(X x) { set(x); } public void set(Bug_Interface x) { } } Directly compiling this will fail as follows: $ ~/GCC/trunk.build.64.install/bin/gcj -c Bug.java Bug.java: In class 'Bug': Bug.java: In constructor '(Bug_Class)': In file included from <built-in>:3: Bug.java:3: error: verification failed at PC=9: incompatible type on stack gcj is able to emit a class file, but that one is considered non-verifying by the BCEL verifier: [...] Pass 3b, method number 0 ['public void <init>(Bug_Class arg1) [Signature(<E:LBug_Class;:LBug_Interface;>(TE;)V)]']: VERIFIED_REJECTED Constraint violated in method 'public void <init>(Bug_Class arg1) [Signature(<E:LBug_Class;:LBug_Interface;>(TE;)V)]': Instruction INVOKEVIRTUAL constraint violated: Expecting a 'Bug_Interface' but found a 'Bug_Class' on the stack (which is not assignment compatible). InstructionHandle: 6: invokevirtual[182](3) 13 [...] What Sun's javac does differently (as per class-file disassembly inspection) is emitting a checkcast against class Bug_Interface before calling invokevirtual. -- Summary: gcj emitting incorrect code Product: gcc Version: 4.3.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: java AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: tschwinge at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38827
next reply other threads:[~2009-01-13 16:03 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-13 16:03 tschwinge at gcc dot gnu dot org [this message] 2009-01-13 19:22 ` [Bug java/38827] " pinskia at gmail dot com 2009-01-13 19:22 ` [Bug java/38827] New: " Andrew Thomas Pinski 2009-01-13 20:37 ` [Bug java/38827] " 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=bug-38827-16947@http.gcc.gnu.org/bugzilla/ \ --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).