aboutsummaryrefslogtreecommitdiffstats
path: root/gcc-4.3.1/INSTALL/test.html
diff options
context:
space:
mode:
Diffstat (limited to 'gcc-4.3.1/INSTALL/test.html')
-rw-r--r--gcc-4.3.1/INSTALL/test.html232
1 files changed, 232 insertions, 0 deletions
diff --git a/gcc-4.3.1/INSTALL/test.html b/gcc-4.3.1/INSTALL/test.html
new file mode 100644
index 000000000..0c5278de6
--- /dev/null
+++ b/gcc-4.3.1/INSTALL/test.html
@@ -0,0 +1,232 @@
+<html lang="en">
+<head>
+<title>Installing GCC: Testing</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="Installing GCC: Testing">
+<meta name="generator" content="makeinfo 4.11">
+<link title="Top" rel="top" href="#Top">
+<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
+<!--
+Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
+1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
+
+ Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, the Front-Cover texts being (a) (see below), and
+with the Back-Cover Texts being (b) (see below). A copy of the
+license is included in the section entitled "GNU Free Documentation License".
+
+(a) The FSF's Front-Cover Text is:
+
+ A GNU Manual
+
+(b) The FSF's Back-Cover Text is:
+
+ You have freedom to copy and modify this GNU Manual, like GNU
+ software. Copies published by the Free Software Foundation raise
+ funds for GNU development.-->
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+ pre.display { font-family:inherit }
+ pre.format { font-family:inherit }
+ pre.smalldisplay { font-family:inherit; font-size:smaller }
+ pre.smallformat { font-family:inherit; font-size:smaller }
+ pre.smallexample { font-size:smaller }
+ pre.smalllisp { font-size:smaller }
+ span.sc { font-variant:small-caps }
+ span.roman { font-family:serif; font-weight:normal; }
+ span.sansserif { font-family:sans-serif; font-weight:normal; }
+--></style>
+</head>
+<body>
+<h1 class="settitle">Installing GCC: Testing</h1>
+<a name="index-Testing-1"></a><a name="index-Installing-GCC_003a-Testing-2"></a><a name="index-Testsuite-3"></a>
+Before you install GCC, we encourage you to run the testsuites and to
+compare your results with results from a similar configuration that have
+been submitted to the
+<a href="http://gcc.gnu.org/ml/gcc-testresults/">gcc-testresults mailing list</a>.
+Some of these archived results are linked from the build status lists
+at <a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>, although not everyone who
+reports a successful build runs the testsuites and submits the results.
+This step is optional and may require you to download additional software,
+but it can give you confidence in your new GCC installation or point out
+problems before you install and start using your new GCC.
+
+ <p>First, you must have <a href="download.html">downloaded the testsuites</a>.
+These are part of the full distribution, but if you downloaded the
+&ldquo;core&rdquo; compiler plus any front ends, you must download the testsuites
+separately.
+
+ <p>Second, you must have the testing tools installed. This includes
+<a href="http://www.gnu.org/software/dejagnu/">DejaGnu</a>, Tcl, and Expect;
+the DejaGnu site has links to these.
+
+ <p>If the directories where <samp><span class="command">runtest</span></samp> and <samp><span class="command">expect</span></samp> were
+installed are not in the <samp><span class="env">PATH</span></samp>, you may need to set the following
+environment variables appropriately, as in the following example (which
+assumes that DejaGnu has been installed under <samp><span class="file">/usr/local</span></samp>):
+
+<pre class="smallexample"> TCL_LIBRARY = /usr/local/share/tcl8.0
+ DEJAGNULIBS = /usr/local/share/dejagnu
+</pre>
+ <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>Finally, you can run the testsuite (which may take a long time):
+<pre class="smallexample"> cd <var>objdir</var>; make -k check
+</pre>
+ <p>This will test various components of GCC, such as compiler
+front ends and runtime libraries. While running the testsuite, DejaGnu
+might emit some harmless messages resembling
+&lsquo;<samp><span class="samp">WARNING: Couldn't find the global config file.</span></samp>&rsquo; or
+&lsquo;<samp><span class="samp">WARNING: Couldn't find tool init file</span></samp>&rsquo; that can be ignored.
+
+ <p>If you are testing a cross-compiler, you may want to run the testsuite
+on a simulator as described at <a href="http://gcc.gnu.org/simtest-howto.html">http://gcc.gnu.org/simtest-howto.html</a>.
+
+<h3 class="section"><a name="TOC0"></a>0.1 How can you run the testsuite on selected tests?</h3>
+
+<p>In order to run sets of tests selectively, there are targets
+&lsquo;<samp><span class="samp">make check-gcc</span></samp>&rsquo; and &lsquo;<samp><span class="samp">make check-g++</span></samp>&rsquo;
+in the <samp><span class="file">gcc</span></samp> subdirectory of the object directory. You can also
+just run &lsquo;<samp><span class="samp">make check</span></samp>&rsquo; in a subdirectory of the object directory.
+
+ <p>A more selective way to just run all <samp><span class="command">gcc</span></samp> execute tests in the
+testsuite is to use
+
+<pre class="smallexample"> make check-gcc RUNTESTFLAGS="execute.exp <var>other-options</var>"
+</pre>
+ <p>Likewise, in order to run only the <samp><span class="command">g++</span></samp> &ldquo;old-deja&rdquo; tests in
+the testsuite with filenames matching &lsquo;<samp><span class="samp">9805*</span></samp>&rsquo;, you would use
+
+<pre class="smallexample"> make check-g++ RUNTESTFLAGS="old-deja.exp=9805* <var>other-options</var>"
+</pre>
+ <p>The <samp><span class="file">*.exp</span></samp> files are located in the testsuite directories of the GCC
+source, the most important ones being <samp><span class="file">compile.exp</span></samp>,
+<samp><span class="file">execute.exp</span></samp>, <samp><span class="file">dg.exp</span></samp> and <samp><span class="file">old-deja.exp</span></samp>.
+To get a list of the possible <samp><span class="file">*.exp</span></samp> files, pipe the
+output of &lsquo;<samp><span class="samp">make check</span></samp>&rsquo; into a file and look at the
+&lsquo;<samp><span class="samp">Running ... .exp</span></samp>&rsquo; lines.
+
+<h3 class="section"><a name="TOC1"></a>0.2 Passing options and running multiple testsuites</h3>
+
+<p>You can pass multiple options to the testsuite using the
+&lsquo;<samp><span class="samp">--target_board</span></samp>&rsquo; option of DejaGNU, either passed as part of
+&lsquo;<samp><span class="samp">RUNTESTFLAGS</span></samp>&rsquo;, or directly to <samp><span class="command">runtest</span></samp> if you prefer to
+work outside the makefiles. For example,
+
+<pre class="smallexample"> make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
+</pre>
+ <p>will run the standard <samp><span class="command">g++</span></samp> testsuites (&ldquo;unix&rdquo; is the target name
+for a standard native testsuite situation), passing
+&lsquo;<samp><span class="samp">-O3 -fmerge-constants</span></samp>&rsquo; to the compiler on every test, i.e.,
+slashes separate options.
+
+ <p>You can run the testsuites multiple times using combinations of options
+with a syntax similar to the brace expansion of popular shells:
+
+<pre class="smallexample"> ..."--target_board=arm-sim\{-mhard-float,-msoft-float\}\{-O1,-O2,-O3,\}"
+</pre>
+ <p>(Note the empty option caused by the trailing comma in the final group.)
+The following will run each testsuite eight times using the &lsquo;<samp><span class="samp">arm-sim</span></samp>&rsquo;
+target, as if you had specified all possible combinations yourself:
+
+<pre class="smallexample"> --target_board=arm-sim/-mhard-float/-O1
+ --target_board=arm-sim/-mhard-float/-O2
+ --target_board=arm-sim/-mhard-float/-O3
+ --target_board=arm-sim/-mhard-float
+ --target_board=arm-sim/-msoft-float/-O1
+ --target_board=arm-sim/-msoft-float/-O2
+ --target_board=arm-sim/-msoft-float/-O3
+ --target_board=arm-sim/-msoft-float
+</pre>
+ <p>They can be combined as many times as you wish, in arbitrary ways. This
+list:
+
+<pre class="smallexample"> ..."--target_board=unix/-Wextra\{-O3,-fno-strength\}\{-fomit-frame,\}"
+</pre>
+ <p>will generate four combinations, all involving &lsquo;<samp><span class="samp">-Wextra</span></samp>&rsquo;.
+
+ <p>The disadvantage to this method is that the testsuites are run in serial,
+which is a waste on multiprocessor systems. For users with GNU Make and
+a shell which performs brace expansion, you can run the testsuites in
+parallel by having the shell perform the combinations and <samp><span class="command">make</span></samp>
+do the parallel runs. Instead of using &lsquo;<samp><span class="samp">--target_board</span></samp>&rsquo;, use a
+special makefile target:
+
+<pre class="smallexample"> make -j<var>N</var> check-<var>testsuite</var>//<var>test-target</var>/<var>option1</var>/<var>option2</var>/...
+</pre>
+ <p>For example,
+
+<pre class="smallexample"> make -j3 check-gcc//sh-hms-sim/{-m1,-m2,-m3,-m3e,-m4}/{,-nofpu}
+</pre>
+ <p>will run three concurrent &ldquo;make-gcc&rdquo; testsuites, eventually testing all
+ten combinations as described above. Note that this is currently only
+supported in the <samp><span class="file">gcc</span></samp> subdirectory. (To see how this works, try
+typing <samp><span class="command">echo</span></samp> before the example given here.)
+
+<h3 class="section"><a name="TOC2"></a>0.3 Additional testing for Java Class Libraries</h3>
+
+<p>The Java runtime tests can be executed via &lsquo;<samp><span class="samp">make check</span></samp>&rsquo;
+in the <samp><var>target</var><span class="file">/libjava/testsuite</span></samp> directory in
+the build tree.
+
+ <p>The <a href="http://sourceware.org/mauve/">Mauve Project</a> provides
+a suite of tests for the Java Class Libraries. This suite can be run
+as part of libgcj testing by placing the Mauve tree within the libjava
+testsuite at <samp><span class="file">libjava/testsuite/libjava.mauve/mauve</span></samp>, or by
+specifying the location of that tree when invoking &lsquo;<samp><span class="samp">make</span></samp>&rsquo;, as in
+&lsquo;<samp><span class="samp">make MAUVEDIR=~/mauve check</span></samp>&rsquo;.
+
+<h3 class="section"><a name="TOC3"></a>0.4 How to interpret test results</h3>
+
+<p>The result of running the testsuite are various <samp><span class="file">*.sum</span></samp> and <samp><span class="file">*.log</span></samp>
+files in the testsuite subdirectories. The <samp><span class="file">*.log</span></samp> files contain a
+detailed log of the compiler invocations and the corresponding
+results, the <samp><span class="file">*.sum</span></samp> files summarize the results. These summaries
+contain status codes for all tests:
+
+ <ul>
+<li>PASS: the test passed as expected
+<li>XPASS: the test unexpectedly passed
+<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 the testing harness does not allow fine grained control
+over whether or not a test is expected to fail. This problem should
+be fixed in future releases.
+
+<h3 class="section"><a name="TOC4"></a>0.5 Submitting test results</h3>
+
+<p>If you want to report the results to the GCC project, use the
+<samp><span class="file">contrib/test_summary</span></samp> shell script. Start it in the <var>objdir</var> with
+
+<pre class="smallexample"> <var>srcdir</var>/contrib/test_summary -p your_commentary.txt \
+ -m gcc-testresults@gcc.gnu.org |sh
+</pre>
+ <p>This script uses the <samp><span class="command">Mail</span></samp> program to send the results, so
+make sure it is in your <samp><span class="env">PATH</span></samp>. The file <samp><span class="file">your_commentary.txt</span></samp> 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 may be automatically processed.
+
+ <p><hr />
+<p><a href="./index.html">Return to the GCC Installation page</a>
+
+<!-- ***Final install*********************************************************** -->
+<!-- ***Binaries**************************************************************** -->
+<!-- ***Specific**************************************************************** -->
+<!-- ***Old documentation****************************************************** -->
+<!-- ***GFDL******************************************************************** -->
+<!-- *************************************************************************** -->
+<!-- Part 6 The End of the Document -->
+</body></html>
+