public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "rmathew at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/14781] New: Need flag to disable bytecode verification Date: Tue, 30 Mar 2004 05:43:00 -0000 [thread overview] Message-ID: <20040330054337.14781.rmathew@hotmail.com> (raw) There is currently no way to disable bytecode verification of loaded classes in gij, except by either commenting out the call to _Jv_VerifyMethod( ) in libjava/resolve.cc or by emptying out the body of that method in libjava/verify.cc and then recompiling the whole of libgcj! Needless to say this is quite tedious. Sun's JVMs support the following flags that should be implemented by gij as well: -noverify Do not do bytecode verification. -verify Verify *all* loaded bytecode. In addition, Sun's JVMs do not verify the classes in the bootstrap CLASSPATH by default, unless explicitly instructed by using the "-verify" flag. Again, gij could benefit from this "optimisation". -- Summary: Need flag to disable bytecode verification Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rmathew at hotmail dot com CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14781
next reply other threads:[~2004-03-30 5:43 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-30 5:43 rmathew at hotmail dot com [this message] 2004-03-30 5:50 ` [Bug libgcj/14781] " pinskia at gcc dot gnu dot org 2004-05-31 14:33 ` rmathew at gcc dot gnu dot org 2004-10-28 17:14 ` tromey at gcc dot gnu dot org 2005-05-25 15:16 ` [Bug libgcj/14781] disable bytecode verification for bootclasspath tromey 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=20040330054337.14781.rmathew@hotmail.com \ --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).