This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
[ecj] Patch: FYI: test less
- From: Tom Tromey <tromey at redhat dot com>
- To: Java Patch List <java-patches at gcc dot gnu dot org>
- Date: 19 Jun 2006 15:49:01 -0600
- Subject: [ecj] Patch: FYI: test less
- Reply-to: tromey at redhat dot com
I'm checking this in on the gcj-eclipse branch.
There doesn't seem to be much point in testing the
compilation-via-bytecode path any more, as we always go via bytecode now.
Tom
Index: ChangeLog
from Tom Tromey <tromey@redhat.com>
* testsuite/lib/libjava.exp (test_libjava): Don't compile via
bytecode. Run BC compilations from source.
Index: testsuite/lib/libjava.exp
===================================================================
--- testsuite/lib/libjava.exp (revision 114413)
+++ testsuite/lib/libjava.exp (working copy)
@@ -910,15 +910,13 @@
#
proc test_libjava { options srcfile compile_args inpfile resultfile exec_args } {
test_libjava_from_source $options $srcfile $compile_args $inpfile $resultfile $exec_args
- test_libjava_from_javac $options $srcfile $compile_args $inpfile $resultfile $exec_args
-
- # Test BC-ABI compilation, currently for bytecode->native only
+
+ # Test BC-ABI compilation.
set compile_args_bcabi $compile_args
lappend compile_args_bcabi "-findirect-dispatch"
+ test_libjava_from_source $options $srcfile $compile_args_bcabi $inpfile $resultfile $exec_args
+}
- test_libjava_from_javac $options $srcfile $compile_args_bcabi $inpfile $resultfile $exec_args
- }
-
#
# libjava_version -- extract and print the version number of libjavap
#