[llvm-commits] CVS: llvm/docs/CFEBuildInstrs.html GettingStarted.html Projects.html TestingGuide.html index.html
John Criswell
criswell at cs.uiuc.edu
Fri Dec 10 07:47:32 PST 2004
Changes in directory llvm/docs:
CFEBuildInstrs.html updated: 1.32 -> 1.33
GettingStarted.html updated: 1.92 -> 1.93
Projects.html updated: 1.12 -> 1.13
TestingGuide.html updated: 1.20 -> 1.21
index.html updated: 1.38 -> 1.39
---
Log message:
Merged in RELEASE_14 changes.
---
Diffs of the changes: (+64 -37)
Index: llvm/docs/CFEBuildInstrs.html
diff -u llvm/docs/CFEBuildInstrs.html:1.32 llvm/docs/CFEBuildInstrs.html:1.33
--- llvm/docs/CFEBuildInstrs.html:1.32 Sat Dec 4 02:13:20 2004
+++ llvm/docs/CFEBuildInstrs.html Fri Dec 10 09:47:17 2004
@@ -45,7 +45,6 @@
<ol>
<li>you really, really, really can't use the binaries we distribute</li>
- <li>you need GCC to fix some of the header files on your system</li>
<li>you are an elite GCC hacker.</li>
</ol>
@@ -59,7 +58,7 @@
<!--=========================================================================-->
<div class="doc_text">
-<p>If you are building LLVM and the C front-end under Cygwin, please note that
+<p>If you are building LLVM and the GCC front-end under Cygwin, please note that
the LLVM and GCC makefiles do not correctly handle spaces in paths. To deal
with this issue, make sure that your LLVM and GCC source and build trees are
located in a top-level directory (like <tt>/cygdrive/c/llvm</tt> and
@@ -76,7 +75,7 @@
<!--=========================================================================-->
<div class="doc_text">
-<p>If you are building LLVM and the C front-end under AIX, do NOT use GNU
+<p>If you are building LLVM and the GCC front-end under AIX, do NOT use GNU
Binutils. They are not stable under AIX and may produce incorrect and/or
invalid code. Instead, use the system assembler and linker.
</p>
@@ -121,7 +120,7 @@
</pre></li>
-<li><p>Configure, build, and install the C front-end:</p>
+<li><p>Configure, build, and install the GCC front-end:</p>
<p>
<b>Linux/x86:</b><br>
@@ -176,7 +175,7 @@
<ul>
<li><p><b>Fix 1:</b> If you have system header files that include
inline assembly, you may have to modify them to remove the inline
- assembly, and install the modified versions in
+ assembly and install the modified versions in
<code>$CFEINSTALL/lib/gcc/<i>target-triplet</i>/3.4-llvm/include</code>.</li>
<li><b>Fix 2:</b> If you are building the C++ front-end on a CPU we
@@ -186,10 +185,10 @@
and apply a patch so that it does not use inline assembly.</li>
</ul>
- <p><b>Porting to a new architecture:</b> If you are porting the new front-end
- to a new architecture, or compiling in a different configuration that we have
- previously, there are probably several changes you will have to make to the GCC
- target to get it to work correctly. These include:<p>
+ <p><b>Porting to a new architecture:</b> If you are porting the front-end
+ to a new architecture or compiling in a configuration that we have
+ not tried previously, there are probably several changes you will have to make
+ to the GCC target to get it to work correctly. These include:<p>
<ul>
<li>Often targets include special assembler or linker flags which
@@ -216,7 +215,7 @@
<li><p>Go back into the LLVM source tree proper. Rerun configure, using
the <code>--with-llvmgccdir=$CFEINSTALL</code> option to specify the path
-to the newly built C front-end.</p></li>
+to the newly built GCC front-end.</p></li>
<li><p>If you edited header files during the C/C++ front-end build as
described in "Fix 1" above, you must now copy those header files from
@@ -228,7 +227,7 @@
<li><p>Rebuild your CVS tree. This shouldn't cause the whole thing to be
rebuilt, but it should build the runtime libraries. After the tree is
- built, install the runtime libraries into your C front-end build tree.
+ built, install the runtime libraries into your GCC front-end build tree.
These are the commands you need.</p>
<pre>
% gmake
@@ -255,8 +254,8 @@
following means:</p>
<ul>
<li> compiling and running a "hello, LLVM" program in C and C++.</li>
- <li> running the tests under <tt>test/Programs</tt> using <code>gmake -C
- test/Programs</code></li>
+ <li> running the regression tests in <tt>llvm/test</tt>
+ <li> running the tests found in the <tt>llvm-test</tt> CVS module</li>
</ul></li>
</ol>
</div>
@@ -333,7 +332,7 @@
Brian Gaeke<br>
<a href="http://llvm.cs.uiuc.edu">LLVM Compiler Infrastructure</a><br>
- Last modified: $Date: 2004/12/04 08:13:20 $
+ Last modified: $Date: 2004/12/10 15:47:17 $
</address>
</body>
Index: llvm/docs/GettingStarted.html
diff -u llvm/docs/GettingStarted.html:1.92 llvm/docs/GettingStarted.html:1.93
--- llvm/docs/GettingStarted.html:1.92 Thu Dec 9 11:55:37 2004
+++ llvm/docs/GettingStarted.html Fri Dec 10 09:47:17 2004
@@ -115,8 +115,7 @@
<ol>
<li><tt>cd <i>where-you-want-the-C-front-end-to-live</i></tt>
<li><tt>gunzip --stdout cfrontend.<i>platform</i>.tar.gz | tar -xvf -</tt>
- <li><b>Sparc and MacOS X Only:</b><br>
- <tt>cd cfrontend/<i>platform</i><br>
+ <li><tt>cd cfrontend/<i>platform</i><br>
./fixheaders</tt>
</ol></li>
@@ -126,7 +125,7 @@
<ol>
<li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
<li><tt>gunzip --stdout llvm-<i>version</i>.tar.gz | tar -xvf -</tt>
- <li><tt>cd llvm</tt>
+ <li><tt>cd llvm</tt></li>
</ol></li>
<li>With anonymous CVS access (or use a <a href="#mirror">mirror</a>):
@@ -142,6 +141,32 @@
</ol></li>
</ul></li>
+ <li>Get the Test Suite Source Code (<em>optional</em>)
+ <ul>
+ <li>With the distributed files:
+ <ol>
+ <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
+ <li><tt>cd llvm/projects</tt>
+ <li><tt>gunzip --stdout llvm-test-<i>version</i>.tar.gz | tar -xvf -</tt>
+ <li><tt>cd ..</tt></li>
+ </ol></li>
+
+ <li>With anonymous CVS access (or use a <a href="#mirror">mirror</a>):
+ <ol>
+ <li><tt>cd <i>where-you-want-llvm-to-live</i></tt></li>
+ <li><tt>cd llvm/projects</tt>
+ <li><tt>cvs -d
+ :pserver:anon at llvm-cvs.cs.uiuc.edu:/var/cvs/llvm login</tt></li>
+ <li>Hit the return key when prompted for the password.
+ <li><tt>cvs -z3 -d :pserver:anon at llvm-cvs.cs.uiuc.edu:/var/cvs/llvm
+ co llvm-test</tt></li>
+ <li><tt>cd llvm-test</tt></li>
+ <li><tt>cvs up -P -d</tt></li>
+ <li><tt>cd ..</tt></li>
+ </ol></li>
+ </ul></li>
+
+
<li>Configure the LLVM Build Environment
<ol>
<li>Change directory to where you want to store the LLVM object
@@ -548,8 +573,9 @@
<p>
If you have the LLVM distribution, you will need to unpack it before you
can begin to compile it. LLVM is distributed as a set of two files: the LLVM
-suite and the LLVM GCC front end compiled for your platform. Each
-file is a TAR archive that is compressed with the gzip program.
+suite and the LLVM GCC front end compiled for your platform. There is an
+additional test suite that is optional. Each file is a TAR archive that is
+compressed with the gzip program.
</p>
<p> The files are as follows:
@@ -573,7 +599,7 @@
<dt><tt>cfrontend-1.4.i386-unknown-freebsd5.1.tar.gz</tt></dt>
<dd>This is the binary release of the GCC front end for FreeBSD/x86.<br/></dd>
- <dt><tt>cfrontend-1.4.powerpc-apple-darwin7.0.0.tar.gz</tt></dt>
+ <dt><tt>cfrontend-1.4.powerpc-apple-darwin7.6.0.tar.gz</tt></dt>
<dd>This is the binary release of the GCC front end for MacOS X/PPC.<br/></dd>
</dl>
@@ -672,8 +698,7 @@
-</tt></li>
</ol>
-<p>If you are using Solaris/Sparc or MacOS X/PPC, you will need to fix the
-header files:</p>
+<p>Next, you will need to fix your system header files:</p>
<p><tt>cd cfrontend/<i>platform</i><br>
./fixheaders</tt></p>
@@ -1478,7 +1503,7 @@
<a href="mailto:sabre at nondot.org">Chris Lattner</a><br>
<a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
<a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
- Last modified: $Date: 2004/12/09 17:55:37 $
+ Last modified: $Date: 2004/12/10 15:47:17 $
</address>
</body>
</html>
Index: llvm/docs/Projects.html
diff -u llvm/docs/Projects.html:1.12 llvm/docs/Projects.html:1.13
--- llvm/docs/Projects.html:1.12 Wed Dec 8 11:25:46 2004
+++ llvm/docs/Projects.html Fri Dec 10 09:47:17 2004
@@ -201,14 +201,14 @@
<p>
<li>
- The LLVM source tree provides benchmarks and programs which are
- known to compile with the LLVM GCC front ends. You can use these
+ LLVM contains an optional package called <tt>llvm-test</tt>
+ which provides benchmarks and programs that are known to compile with the
+ LLVM GCC front ends. You can use these
programs to test your code, gather statistics information, and
- compare it to the current LLVM performance statistics. These
- programs are found in the <tt>llvm/test/Programs</tt> directory.
+ compare it to the current LLVM performance statistics.
<p>
Currently, there is no way to hook your tests directly into the
- <tt>llvm/test/Programs</tt> testing harness. You will simply
+ <tt>llvm/test</tt> testing harness. You will simply
need to find a way to use the source provided within that directory
on your own.
</ul>
@@ -443,7 +443,7 @@
<a href="mailto:criswell at uiuc.edu">John Criswell</a><br>
<a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a>
<br>
- Last modified: $Date: 2004/12/08 17:25:46 $
+ Last modified: $Date: 2004/12/10 15:47:17 $
</address>
</body>
Index: llvm/docs/TestingGuide.html
diff -u llvm/docs/TestingGuide.html:1.20 llvm/docs/TestingGuide.html:1.21
--- llvm/docs/TestingGuide.html:1.20 Wed Dec 8 11:37:21 2004
+++ llvm/docs/TestingGuide.html Fri Dec 10 09:47:17 2004
@@ -102,7 +102,7 @@
programs in C and C++ is in the <tt>llvm-test</tt> module. This module should
be checked out to the <tt>llvm/projects</tt> directory. When you
<tt>configure</tt> the <tt>llvm</tt> module, the <tt>llvm-test</tt> module
-will be automatically configured. Or you can do it manually.</p>
+will be automatically configured. Alternatively, you can configure the <tt>llvm-test</tt> module manually.</p>
<p>To run all of the simple tests in LLVM using DejaGNU, use the master Makefile in the
<tt>llvm/test</tt> directory:</p>
<pre>
@@ -140,7 +140,7 @@
<p>The LLVM test suite contains two major categories of tests: code
fragments and whole programs. Code fragments are in the <tt>llvm</tt> module
under the directory under the <tt>llvm/test</tt> directory. The whole programs
-test suite are n the <tt>llvm-test</tt> module under the main directory.</p>
+test suite are in the <tt>llvm-test</tt> module under the main directory.</p>
</div>
@@ -251,12 +251,13 @@
<div class="doc_text">
<p>The LLVM test suite is partially driven by DejaGNU and partially
driven by GNU Make. Specifically, the Features and Regression tests
-are all driven by DejaGNU. The llvm-test
+are all driven by DejaGNU. The <tt>llvm-test</tt>
module is currently driven by a set of Makefiles.</p>
<p>The DejaGNU structure is very simple, but does require some
-information to be set. This information is gathered via configure and
-is written to a file, <tt>site.exp</tt> in llvm/test. The llvm/test
+information to be set. This information is gathered via <tt>configure</tt> and
+is written to a file, <tt>site.exp</tt> in <tt>llvm/test</tt>. The
+<tt>llvm/test</tt>
Makefile does this work for you.</p>
<p>In order for DejaGNU to work, each directory of tests must have a
@@ -392,7 +393,8 @@
tests. By default, it will run all of these tests.</p>
<p>To run only the DejaGNU driven tests, run <tt>gmake</tt> at the
-command line in llvm/tests. To run a specific directory of tests, specify the TESTSUITE.
+command line in llvm/tests. To run a specific directory of tests, use the
+TESTSUITE variable.
</p>
<p>For example, to run the Regression tests, type
@@ -511,7 +513,7 @@
John T. Criswell<br>
<a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br/>
- Last modified: $Date: 2004/12/08 17:37:21 $
+ Last modified: $Date: 2004/12/10 15:47:17 $
</address>
</body>
</html>
Index: llvm/docs/index.html
diff -u llvm/docs/index.html:1.38 llvm/docs/index.html:1.39
--- llvm/docs/index.html:1.38 Thu Dec 9 14:26:53 2004
+++ llvm/docs/index.html Fri Dec 10 09:47:17 2004
@@ -55,6 +55,7 @@
manual for the LLVM command line utilities ("man" pages for LLVM tools).<br/>
Current tools:
<a href="CommandGuide/html/llvm-ar.html">llvm-ar</a>,
+ <a href="CommandGuide/html/llvm-ranlib.html">llvm-ranlib</a>,
<a href="CommandGuide/html/llvm-as.html">llvm-as</a>,
<a href="CommandGuide/html/llvm-dis.html">llvm-dis</a>,
<a href="CommandGuide/html/opt.html">opt</a>,
@@ -229,6 +230,6 @@
src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"></a>
<a href="http://llvm.cs.uiuc.edu">LLVM Compiler Infrastructure</a><br>
- Last modified: $Date: 2004/12/09 20:26:53 $
+ Last modified: $Date: 2004/12/10 15:47:17 $
</address>
More information about the llvm-commits
mailing list