Ignore:
Timestamp:
Apr 27, 2004, 8:39:34 PM (21 years ago)
Author:
bird
Message:

GCC v3.3.3 sources.

Location:
branches/GNU/src/gcc
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • branches/GNU/src/gcc

    • Property svn:ignore

      •  

        old new  
        2626configure.vr
        2727configure.vrs
         28dir.info
        2829Makefile
        29 dir.info
        3030lost+found
        3131update.out

  • branches/GNU/src/gcc/INSTALL/test.html

    • Property cvs2svn:cvs-rev changed from 1.1 to 1.1.1.2
    r1390 r1391  
    1 <html lang="en"><head>
     1   <html lang="en">
     2<head>
    23<title>Installing GCC: Testing</title>
    34<meta http-equiv="Content-Type" content="text/html">
    4 <meta name=description content="Installing GCC: Testing">
    5 <meta name=generator content="makeinfo 4.0">
    6 <link href="http://texinfo.org/" rel=generator-home>
    7 </head><body>
     5<meta name="description" content="Installing GCC: Testing">
     6<meta name="generator" content="makeinfo 4.6">
     7<!--
     8Copyright &copy; 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
     91999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
     10<br><p>
     11   <p>Permission is granted to copy, distribute and/or modify this document
     12under the terms of the GNU Free Documentation License, Version 1.2 or
     13any later version published by the Free Software Foundation; with no
     14Invariant Sections, the Front-Cover texts being (a) (see below), and
     15with the Back-Cover Texts being (b) (see below).  A copy of the
     16license is included in the section entitled "<a href="./gfdl.html">GNU Free Documentation License</a>".
    817
    9 <p>B<p>efore you install GCC, we encourage you to run the testsuites and to
     18   <p>(a) The FSF's Front-Cover Text is:
     19
     20   <p>A GNU Manual
     21
     22   <p>(b) The FSF's Back-Cover Text is:
     23
     24   <p>You have freedom to copy and modify this GNU Manual, like GNU
     25     software.  Copies published by the Free Software Foundation raise
     26     funds for GNU development.-->
     27<meta http-equiv="Content-Style-Type" content="text/css">
     28<style type="text/css"><!--
     29  pre.display { font-family:inherit }
     30  pre.format  { font-family:inherit }
     31  pre.smalldisplay { font-family:inherit; font-size:smaller }
     32  pre.smallformat  { font-family:inherit; font-size:smaller }
     33  pre.smallexample { font-size:smaller }
     34  pre.smalllisp    { font-size:smaller }
     35--></style>
     36</head>
     37<body>
     38<h1 class="settitle">Installing GCC: Testing</h1>
     39Before you install GCC, we encourage you to run the testsuites and to
    1040compare your results with results from a similar configuration that have
    1141been submitted to the
    1242<a href="http://gcc.gnu.org/ml/gcc-testresults/">gcc-testresults mailing list</a>.
     43Some of these archived results are linked from the build status lists
     44at <a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>, although not everyone who
     45reports a successful build runs the testsuites and submits the results.
    1346This step is optional and may require you to download additional software,
    1447but it can give you confidence in your new GCC installation or point out
    1548problems before you install and start using your new GCC.
    1649
    17 <p>First, you must have <a href="download.html">downloaded the testsuites</a>.
     50   <p>First, you must have <a href="download.html">downloaded the testsuites</a>.
    1851These are part of the full distribution, but if you downloaded the
    1952"core" compiler plus any front ends, you must download the testsuites
    2053separately.
    2154
    22 <p>Second, you must have the testing tools installed.  This includes
    23 a <a href="http://www.gnu.org/software/dejagnu/">current version of DejaGnu</a>;
    24 dejagnu 1.3 is not sufficient.
    25 It also includes Tcl and Expect; the DejaGnu site has links to these.
     55   <p>Second, you must have the testing tools installed.  This includes
     56<a href="http://www.gnu.org/software/dejagnu/">DejaGnu</a> 1.4.1 or 1.4.3
     57and later, Tcl, and Expect; the DejaGnu site has links to these.
    2658
    27 <p>Now you may need specific preparations:
     59   <p>If the directories where <code>runtest</code> and <code>expect</code> were
     60installed are not in the <code>PATH</code>, you may need to set the following
     61environment variables appropriately, as in the following example (which
     62assumes that DejaGnu has been installed under <code>/usr/local</code>):
    2863
    29 <ul>
     64<pre class="example">          TCL_LIBRARY = /usr/local/share/tcl8.0
     65          DEJAGNULIBS = /usr/local/share/dejagnu
     66     </pre>
    3067
    31 <li>The following environment variables may need to be set appropriately, as in
    32 the following example (which assumes that DejaGnu has been installed
    33 under <code>/usr/local</code>):
     68   <p>(On systems such as Cygwin, these paths are required to be actual
     69paths, not mounts or links; presumably this is due to some lack of
     70portability in the DejaGnu code.)
    3471
    35 <pre>     TCL_LIBRARY = /usr/local/share/tcl8.0
    36      DEJAGNULIBS = /usr/local/share/dejagnu
    37 </pre>
     72   <p>Finally, you can run the testsuite (which may take a long time):
     73<pre class="example">          cd <var>objdir</var>; make -k check
     74     </pre>
    3875
    39 <p>On systems such as Cygwin, these paths are required to be actual
    40 paths, not mounts or links; presumably this is due to some lack of
    41 portability in the DejaGnu code.
     76   <p>This will test various components of GCC, such as compiler
     77front ends and runtime libraries.  While running the testsuite, DejaGnu
     78might emit some harmless messages resembling
     79<code>WARNING: Couldn't find the global config file.</code> or
     80<code>WARNING: Couldn't find tool init file</code> that can be ignored.
    4281
    43 <p>If the directories where <code>runtest</code> and <code>expect</code> were
    44 installed are in the <code>PATH</code>, it should not be necessary to set these
    45 environment variables.
     82<h3 class="section"><a name="TOC0"></a>How can I run the test suite on selected tests?</h3>
    4683
    47 </ul>
     84<p>In order to run sets of tests selectively, there are targets
     85<code>make check-gcc</code> and <code>make check-g++</code>
     86in the <code>gcc</code> subdirectory of the object directory.  You can also
     87just run <code>make check</code> in a subdirectory of the object directory.
    4888
    49 <p>Finally, you can run the testsuite (which may take a long time):
    50 <pre>     cd <var>objdir</var>; make -k check
    51 </pre>
     89   <p>A more selective way to just run all <code>gcc</code> execute tests in the
     90testsuite is to use
    5291
    53 <p>The testing process will try to test as many components in the GCC
    54 distribution as possible, including the C, C++, Objective-C and Fortran
    55 compilers as well as the C++ and Java runtime libraries.
     92<pre class="example">         make check-gcc RUNTESTFLAGS="execute.exp <var>other-options</var>"
     93     </pre>
    5694
    57 <p>While running the testsuite, DejaGnu might emit messages resembling
    58 <code>WARNING: Couldn't find the global config file.</code> or
    59 <code>WARNING: Couldn't find tool init file</code>.
    60 These messages are harmless and do not affect the validity of the tests.
     95   <p>Likewise, in order to run only the <code>g++</code> "old-deja" tests in
     96the testsuite with filenames matching <code>9805*</code>, you would use
    6197
    62 <h2><a name="TOC0">How can I run the test suite on selected tests?</h2>
     98<pre class="example">         make check-g++ RUNTESTFLAGS="old-deja.exp=9805* <var>other-options</var>"
     99     </pre>
    63100
    64 <p>As a first possibility to cut down the number of tests that are run it is
    65 possible to use <code>make check-gcc</code> or <code>make check-g++</code>
    66 in the <code>gcc</code> subdirectory of the object directory.  To further cut down the
    67 tests the following is possible:
    68 
    69 <pre>    make check-gcc RUNTESTFLAGS="execute.exp <var>other-options</var>"
    70 </pre>
    71 
    72 <p>This will run all <code>gcc</code> execute tests in the testsuite.
    73 
    74 <pre>    make check-g++ RUNTESTFLAGS="old-deja.exp=9805* <var>other-options</var>"
    75 </pre>
    76 
    77 <p>This will run the <code>g++</code> "old-deja" tests in the testsuite where the filename
    78 matches <code>9805*</code>.
    79 
    80 <p>The <code>*.exp</code> files are located in the testsuite directories of the GCC
     101   <p>The <code>*.exp</code> files are located in the testsuite directories of the GCC
    81102source, the most important ones being <code>compile.exp</code>,
    82103<code>execute.exp</code>, <code>dg.exp</code> and <code>old-deja.exp</code>.
    83104To get a list of the possible <code>*.exp</code> files, pipe the
    84105output of <code>make check</code> into a file and look at the
    85 <code>Running <small>...</small>  .exp</code> lines.
     106<code>Running ...  .exp</code> lines.
    86107
    87 <p>To run only the tests for a library, run <code>make check</code> from the
    88 the library's testsuite in a subdirectory of the object directory:
    89 <code>libstdc++-v3/testsuite</code> or <code>libcgj/testsuite</code>.
     108   <p>The Java runtime tests can be executed via <code>make check</code>
     109in the <code></code><var>target</var><code>/libjava/testsuite</code> directory in
     110the build tree.
    90111
    91 <h2><a name="TOC1">Additional testing for Java Class Libraries</h2>
     112<h3 class="section"><a name="TOC1"></a>Additional testing for Java Class Libraries</h3>
    92113
    93114<p>The <a href="http://sources.redhat.com/mauve/">Mauve Project</a> provides
    94115a suite of tests for the Java Class Libraries.  This suite can be run
    95 as part of libgcj testing by specifying the location of the Mauve tree
    96 when invoking <code>make</code>, as in <code>make MAUVEDIR=~/mauve check</code>.
     116as part of libgcj testing by placing the Mauve tree within the libjava
     117testsuite at <code>libjava/testsuite/libjava.mauve/mauve</code>, or by
     118specifying the location of that tree when invoking <code>make</code>, as in
     119<code>make MAUVEDIR=~/mauve check</code>.
    97120
    98 <h2><a name="TOC2">How to interpret test results</h2>
     121   <a href="http://www-124.ibm.com/developerworks/oss/cvs/jikes/~checkout~/jacks/jacks.html">Jacks</a>
     122is a free test suite that tests Java compiler front ends.  This suite
     123can be run as part of libgcj testing by placing the Jacks tree within
     124the libjava testsuite at <code>libjava/testsuite/libjava.jacks/jacks</code>.
    99125
    100 <p>After the testsuite has run you'll find various <code>*.sum</code> and <code>*.log</code>
     126<h3 class="section"><a name="TOC2"></a>How to interpret test results</h3>
     127
     128<p>The result of running the testsuite are various <code>*.sum</code> and <code>*.log</code>
    101129files in the testsuite subdirectories.  The <code>*.log</code> files contain a
    102130detailed log of the compiler invocations and the corresponding
    103 results, the <code>*.sum</code> files summarize the results.  These summaries list
    104 all the tests that have been run with a corresponding status code:
     131results, the <code>*.sum</code> files summarize the results.  These summaries
     132contain status codes for all tests:
    105133
    106 <ul>
     134     <ul>
    107135<li>PASS: the test passed as expected
    108136<li>XPASS: the test unexpectedly passed
    … …  
    114142</ul>
    115143
    116 <p>It is normal for some tests to report unexpected failures.  At the
     144   <p>It is normal for some tests to report unexpected failures.  At the
    117145current time our testing harness does not allow fine grained control
    118146over whether or not a test is expected to fail.  We expect to fix this
    119147problem in future releases.
    120148
    121 <h2><a name="TOC3">Submitting test results</h2>
     149<h3 class="section"><a name="TOC3"></a>Submitting test results</h3>
    122150
    123151<p>If you want to report the results to the GCC project, use the
    124152<code>contrib/test_summary</code> shell script.  Start it in the <var>objdir</var> with
    125153
    126 <pre>    <var>srcdir</var>/contrib/test_summary -p your_commentary.txt \
    127         -m gcc-testresults@gcc.gnu.org |sh
    128 </pre>
     154<pre class="example">         <var>srcdir</var>/contrib/test_summary -p your_commentary.txt \
     155             -m gcc-testresults@gcc.gnu.org |sh
     156     </pre>
    129157
    130 <p>This script uses the <code>Mail</code> program to send the results, so
     158   <p>This script uses the <code>Mail</code> program to send the results, so
    131159make sure it is in your <code>PATH</code>.  The file <code>your_commentary.txt</code> is
    132160prepended to the testsuite summary and should contain any special
    133161remarks you have on your results or your build environment.  Please
    134162do not edit the testsuite result block or the subject line, as these
    135 messages are automatically parsed and presented at the
    136 <a href="http://gcc.gnu.org/testresults/">GCC testresults</a> web
    137 page.  Here you can also gather information on how specific tests
    138 behave on different platforms and compare them with your results.  A
    139 few failing testcases are possible even on released versions and you
    140 should look here first if you think your results are unreasonable.
     163messages may be automatically processed.
    141164
    142 <hr />
     165   <hr />
    143166<p>
    144167<a href="./index.html">Return to the GCC Installation page</a>
    145168
    146 </body></html>
     169   </body></html>
    147170
Note: See TracChangeset for help on using the changeset viewer.