diff options
Diffstat (limited to 'gnu/egcs/install/test.html')
| -rw-r--r-- | gnu/egcs/install/test.html | 131 |
1 files changed, 122 insertions, 9 deletions
diff --git a/gnu/egcs/install/test.html b/gnu/egcs/install/test.html index 4113bb3c4d1..b1774de94fd 100644 --- a/gnu/egcs/install/test.html +++ b/gnu/egcs/install/test.html @@ -1,21 +1,134 @@ <html> + <head> -<title>Installation Instructions: Testing GCC</title> +<title>Installing GCC: Testing</title> </head> <body> -<h1 align="center">Installation Instructions: Testing GCC</h1> +<h1 align="center">Installing GCC: Testing</h1> + +<p><strong>Please note that this is only applicable to current development +versions of GCC and GCC 3.0 or later. GCC 2.95.x does not come with a +testsuite.</strong></p> + +<p>Before you install GCC, you might wish to run the testsuite. This +step is optional and may require you to download additional software.</p> + +<p>First, you must have <a href="download.html">downloaded the +testsuites</a>. The full distribution contains testsuites; only if you +downloaded the "core" compiler plus any front ends, you do not have the +testsuites.</p> + +<p>Second, you must have a new version of dejagnu on your system; +dejagnu 1.3 will not work. We have made dejagnu snapshots available at +<a href="ftp://gcc.gnu.org/pub/gcc/infrastructure">ftp://gcc.gnu.org/pub/gcc/infrastructure</a> +until a new version of dejagnu has been released.</p> + +<p>A few targets require specific preparations:</p> + +<ul> + +<li> +In order to run the libio tests on targets which do not fully +support Unix/POSIX commands (e.g. Cgwin), the references to the dbz +directory may be deleted from libio/configure.in. +</li> + +<li> +<p>When there is difficulty resolving paths to the files init.tcl and +runtest.exp, the following environment variables should be set +appropriately, for example:</p> + +<blockquote><code> +TCL_LIBRARY = /usr/share/tcl8.0<br> +DEJAGNULIBS = /usr/share/dejagnu +</code></blockquote> + +<p>On systems such as Cygwin, these paths are required to be actual +paths, not mounts or links; presumably this is due to some lack of +portability in the dejagnu code.</p> +</li> +</ul> + +<p>Finally, you can run the testsuite (which may take a long time):</p> +<blockquote><code> +cd <i>objdir</i>; make -k check +</code></blockquote> + +<p>The testing process will try to test as many components in the GCC +distribution as possible, including the C, C++ and Fortran compilers as +well as the C++ runtime libraries.</p> + + +<h2>How can I run the test suite on selected tests?</h2> + +<p>As a first possibility to cut down the number of tests that are run it is +possible to use `<code>make check-gcc</code>` or `<code>make check-g++</code>` +in the gcc subdirectory of the object directory. To further cut down the +tests the following is possible:</p> + +<blockquote><code> + make check-gcc RUNTESTFLAGS="execute.exp <other options>" +</code></blockquote> + +<p>This will run all gcc execute tests in the testsuite.</p> + +<blockquote><code> + make check-g++ RUNTESTFLAGS="old-deja.exp=9805* <other options>" +</code></blockquote> + +<p>This will run the g++ "old-deja" tests in the testsuite where the filename +matches 9805*.</p> + +<p>The *.exp files are located in the testsuite directories of the GCC +source, the most important ones being compile.exp, execute.exp, dg.exp +and old-deja.exp. To get a list of the possible *.exp files, pipe the +output of `<code>make check</code>` into a file and look at the +"<code>Running ... .exp</code>" lines. + + +<h2>How to interpret test results</h2> + +<p>After the testsuite has run you'll find various *.sum and *.log +files in the testsuite subdirectories. The *.log files contain a +detailed log of the compiler invocations and the corresponding +results, the *.sum files summarize the results. These summaries list +all the tests that have been run with a corresponding status code:</p> + +<ul> +<li>PASS: the test passed as expected +<li>FAIL: the test unexpectedly failed +<li>XFAIL: the test failed as expected +<li>UNSUPPORTED: the test is not supported on this platform +<li>ERROR: the testsuite detected an error +<li>WARNING: the testsuite detected a possible problem +</ul> + +<p> It is normal for some tests to report +unexpected failures. At the current time our testing harness does not allow +fine grained control over whether or not a test is expected to fail. We expect +to fix this problem in future releases.</p> -<p>The testsuite has been temporarily removed from the gcc distributions -until the copyright status of some tests can be determined. It is hoped -that the testsuite will be included in the gcc releases again soon. -<p>Until the testsuite is included it is impossible to run the testsuite. -Sorry. +<h2>Submitting test results</h2> +<p>If you want to report the results to the GCC project, use the +<code>contrib/test_summary</code> shell script. Start it in the objdir with</p> +<blockquote><code> +<i>srcdir</i>/contrib/test_summary -p your_commentary.txt -m gcc-testresults@gcc.gnu.org |sh +</code></blockquote> -<hr> -<i>Last modified on July 15, 1999.</i> +<p>This script uses the <code>Mail</code> program to send the results, so +make sure it is in your PATH. The file your_commentary.txt is +prepended to the testsuite summary and should contain any special +remarks you have on your results or your build environment. Please +do not edit the testsuite result block or the subject line, as these +messages are automatically parsed and presented at the <a +href="http://gcc.gnu.org/testresults/">GCC testresults</a> web +page. Here you can also gather information on how specific tests +behave on different platforms and compare them with your results. A +few failing testcases are possible even on released versions and you +should look here first if you think your results are unreasonable.</p> </body> </html> |