This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] merge java/test.html into install.texi and sourcebuild.texi
On Wed, Nov 13, 2002 at 01:01:57PM -0700, Tom Tromey wrote:
> >>>>> "Janis" == Janis Johnson <janis187@us.ibm.com> writes:
>
> Janis> Here's what I've now got for the mainline. Tom, is all of this
> Janis> relevant for the branch except the part about putting the mauve
> Janis> or jacks directories in the testsuite sources?
>
> Yes.
OK, here's what went into the 3.2 branch.
I realized that I should have put information into install.texi for
the mainline about running Mauve and Jacks by putting their trees into
the source tree; I'll do that soon.
2002-11-13 Janis Johnson <janis187@us.ibm.com>
* doc/install.texi (Testing): Document extra Java testing.
* doc/sourcebuild.texi (Test Suites): Document libgcj testing.
Index: doc/install.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v
retrieving revision 1.92.2.29.2.9
retrieving revision 1.92.2.29.2.10
diff -u -p -r1.92.2.29.2.9 -r1.92.2.29.2.10
--- doc/install.texi 12 Nov 2002 21:13:25 -0000 1.92.2.29.2.9
+++ doc/install.texi 13 Nov 2002 21:17:09 -0000 1.92.2.29.2.10
@@ -1228,6 +1228,17 @@ To get a list of the possible @file{*.ex
output of @samp{make check} into a file and look at the
@samp{Running @dots{} .exp} lines.
+To run only the tests for a library, run @samp{make check} from the
+the library's testsuite in a subdirectory of the object directory:
+@file{libstdc++-v3/testsuite} or @file{libcgj/testsuite}.
+
+@section Additional testing for Java Class Libraries
+
+The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
+a suite of tests for the Java Class Libraries. This suite can be run
+as part of libgcj testing by specifying the location of the Mauve tree
+when invoking @samp{make}, as in @samp{make MAUVEDIR=~/mauve check}.
+
@section How to interpret test results
After the testsuite has run you'll find various @file{*.sum} and @file{*.log}
Index: doc/sourcebuild.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/sourcebuild.texi,v
retrieving revision 1.3.4.2
retrieving revision 1.3.4.2.4.1
diff -u -p -r1.3.4.2 -r1.3.4.2.4.1
--- doc/sourcebuild.texi 15 Apr 2002 18:59:52 -0000 1.3.4.2
+++ doc/sourcebuild.texi 13 Nov 2002 21:17:09 -0000 1.3.4.2.4.1
@@ -738,6 +738,7 @@ here; FIXME: document the others.
@menu
* Test Idioms:: Idioms used in test suite code.
* C Tests:: The C language test suites.
+* libgcj Tests:: The Java library test suites.
@end menu
@node Test Idioms
@@ -870,3 +871,23 @@ shouldn't.
FIXME: merge in @file{testsuite/README.gcc} and discuss the format of
test cases and magic comments more.
+
+@node libgcj Tests
+@subsection The Java library test suites.
+
+Runtime tests are executed via @samp{make check} from the @samp{testsuite}
+directory of the libjava hierarchy in the build tree. Additional runtime
+tests can be checked into this testsuite.
+
+Regression testing of the core packages in libgcj is also covered by the
+Mauve test suite. The @uref{http://sources.redhat.com/mauve/,,Mauve Project}
+develops tests for the Java Class Libraries. These tests are run as part
+of libgcj testing by specifying the location of the Mauve tree when invoking
+@samp{make}, as in @samp{make MAUVEDIR=~/mauve check}.
+
+The @uref{http://oss.software.ibm.com/developerworks/opensource/jacks/,,
+Jacks} project provides a test suite for Java compilers that can be used
+to test changes that affect the GCJ front end. There is no automated
+mechanism to run the Jacks suite as part of GCJ testing.
+
+We encourage developers to contribute test cases to Mauve and Jacks.