6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-11-01 00:11:00 +00:00
Code Issues Projects Releases Wiki Activity

Update the docs for some of the test-suite configure changes and

Browse Source 
be more clear about what to do and how to do it.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@145426 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Eric Christopher 2011-11-29 19:40:56 +00:00
parent ae6f2cb1fc
commit fe2cb3e37f
1 changed files with 11 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
docs/TestingGuide.html
View File

@ -253,40 +253,35 @@ programs), first checkout and setup the <tt>test-suite</tt> module:</p>
<div class="doc_code">
<pre>
% cd llvm/projects
% cd ~/llvm/projects
% svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
% cd ..
% ./configure --with-llvmgccdir=$LLVM_GCC_DIR
</pre>
</div>
<p>where <tt>$LLVM_GCC_DIR</tt> is the directory where
you <em>installed</em> llvm-gcc, not its src or obj
dir. The <tt>--with-llvmgccdir</tt> option assumes that
the <tt>llvm-gcc-4.2</tt> module was configured with
<tt>--program-prefix=llvm-</tt>, and therefore that the C and C++
compiler drivers are called <tt>llvm-gcc</tt> and <tt>llvm-g++</tt>
respectively. If this is not the case,
use <tt>--with-llvmgcc</tt>/<tt>--with-llvmgxx</tt> to specify each
executable's location.</p>
<p>and then configure and build normally as you would from the
<a href="http://llvm.org/docs/GettingStarted.html#quickstart">Getting Started
Guide</a>. This will autodetect first the built clang if you are building
clang, then <tt>clang</tt> in your path and finally look for <tt>llvm-gcc</tt>
in your path.
<p>Then, run the entire test suite by running make in the <tt>test-suite</tt>
directory:</p>
subdirectory of your build directory:</p>
<div class="doc_code">
<pre>
% cd projects/test-suite
% cd <i>where-you-built-llvm</i>/projects/test-suite
% gmake
</pre>
</div>
<p>Usually, running the "nightly" set of tests is a good idea, and you can also
<p>Usually, running the "simple" set of tests is a good idea, and you can also
let it generate a report by running:</p>
<div class="doc_code">
<pre>
% cd projects/test-suite
% gmake TEST=nightly report report.html
% cd <i>where-you-built-llvm</i>/projects/test-suite
% gmake TEST=simple report report.html
</pre>
</div>