This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Patch: 4.0: Always use new verifier by default
- From: Bryce McKinlay <mckinlay at redhat dot com>
- To: Java Patches <java-patches at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 12 Oct 2005 22:06:38 -0400
- Subject: Patch: 4.0: Always use new verifier by default
The new verifier has been enabled by default for some time, both on HEAD
and when -findirect-dispatch is used. This patch makes it "always on"
for the 4.0 branch, even when -findirect-dispatch is not in use. This
will help people who still run in to the various bugs with the old
verifier ;-)
The old verifier code has been removed completely on HEAD, however I
decided to take the less invasive approach here. This means we don't
break compatibility with the -fnew-verifier command line option on the
4.0 branch.
I'm checking this in.
Bryce
2005-10-12 Bryce McKinlay <mckinlay@redhat.com>
* lang.c (flag_new_verifier): Set on by default.
(java_post_options): Don't need to set flag_new_verifier.
2005-10-12 Bryce McKinlay <mckinlay@redhat.com>
* testsuite/libjava.lang/pr13107_2.xfail: Remove xfail.
* testsuite/libjava.lang/pr13107_3.xfail: Likewise.
Index: lang.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/java/lang.c,v
retrieving revision 1.166
diff -u -r1.166 lang.c
--- lang.c 3 Dec 2004 19:43:51 -0000 1.166
+++ lang.c 13 Oct 2005 01:57:10 -0000
@@ -140,7 +140,7 @@
int flag_verify_invocations = 0;
/* True if the new bytecode verifier should be used. */
-int flag_new_verifier = 0;
+int flag_new_verifier = 1;
/* When nonzero, print extra version information. */
static int v_flag = 0;
@@ -611,12 +611,6 @@
must always verify everything. */
if (! flag_indirect_dispatch)
flag_verify_invocations = true;
- else
- {
- /* If we are using indirect dispatch, then we want the new
- verifier as well. */
- flag_new_verifier = 1;
- }
/* Open input file. */