public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mark at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcj/18036] New: Bad interaction between interpreter and Class.forName() Date: Sat, 16 Oct 2004 20:27:00 -0000 [thread overview] Message-ID: <20041016202755.18036.mark@gcc.gnu.org> (raw) The following code creates a user defined classloader which is then used to load a simple class C from byte code. An instance of this class is created and from this instance Class.forName("C") is called. This should result in the same class object from the same (user defined) classloader. It does work when compiled to native code. But it fails when compiled to byte code and run with gij. With gij 3.4 it works correctly. Current CVS gcj (GCC) 4.0.0 20041016 (experimental) fails Expected output: true true true -- Summary: Bad interaction between interpreter and Class.forName() Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mark at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org GCC host triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18036
next reply other threads:[~2004-10-16 20:27 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-16 20:27 mark at gcc dot gnu dot org [this message] 2004-10-16 22:17 ` [Bug libgcj/18036] " pinskia at gcc dot gnu dot org 2004-10-17 8:52 ` mark at gcc dot gnu dot org 2004-10-18 10:49 ` aph at gcc dot gnu dot org 2004-10-18 14:07 ` cvs-commit at gcc dot gnu dot org 2004-10-18 14:26 ` cvs-commit at gcc dot gnu dot org 2004-10-18 14:39 ` pinskia at gcc dot gnu dot org 2004-10-21 13:22 ` aph at gcc dot gnu dot org 2004-10-21 13:42 ` aph at gcc dot gnu dot org 2005-01-05 9:59 ` cvs-commit 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=20041016202755.18036.mark@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).