[llvm-commits] [release_17] CVS: llvm/docs/BytecodeFormat.html GettingStarted.html GettingStartedVS.html ReleaseNotes.html UsingLibraries.html
Tanya Brethour
tbrethou at cs.uiuc.edu
Wed Apr 19 22:09:29 PDT 2006
Changes in directory llvm/docs:
BytecodeFormat.html updated: 1.51 -> 1.51.2.1
GettingStarted.html updated: 1.128 -> 1.128.2.1
GettingStartedVS.html updated: 1.6 -> 1.6.2.1
ReleaseNotes.html updated: 1.347 -> 1.347.2.1
UsingLibraries.html updated: 1.19 -> 1.19.2.1
---
Log message:
Checking in updates from mainline for 1.7 release.
---
Diffs of the changes: (+263 -80)
BytecodeFormat.html | 4
GettingStarted.html | 44 ++-----
GettingStartedVS.html | 4
ReleaseNotes.html | 287 +++++++++++++++++++++++++++++++++++++++++---------
UsingLibraries.html | 4
5 files changed, 263 insertions(+), 80 deletions(-)
Index: llvm/docs/BytecodeFormat.html
diff -u llvm/docs/BytecodeFormat.html:1.51 llvm/docs/BytecodeFormat.html:1.51.2.1
--- llvm/docs/BytecodeFormat.html:1.51 Mon Mar 13 23:39:39 2006
+++ llvm/docs/BytecodeFormat.html Thu Apr 20 00:09:16 2006
@@ -742,7 +742,7 @@
<li>#2: LLVM 1.2.5 (not released)</li>
<li>#3: LLVM 1.3</li>
<li>#4: LLVM 1.3.x (not released)</li>
- <li>#5: LLVM 1.4, 1.5, 1.6</li>
+ <li>#5: LLVM 1.4 and newer</li>
</li>
</ul>
<p>Note that we plan to eventually expand the target description
@@ -2148,7 +2148,7 @@
<a href="mailto:rspencer at x10sys.com">Reid Spencer</a> and <a
href="mailto:sabre at nondot.org">Chris Lattner</a><br>
<a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
-Last modified: $Date: 2006/03/14 05:39:39 $
+Last modified: $Date: 2006/04/20 05:09:16 $
</address>
</body>
</html>
Index: llvm/docs/GettingStarted.html
diff -u llvm/docs/GettingStarted.html:1.128 llvm/docs/GettingStarted.html:1.128.2.1
--- llvm/docs/GettingStarted.html:1.128 Sun Apr 9 18:45:37 2006
+++ llvm/docs/GettingStarted.html Thu Apr 20 00:09:16 2006
@@ -232,6 +232,12 @@
<td>GCC</td>
</tr>
<tr>
+ <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
+ <td>x86</td>
+ <td>GCC</td>
+
+</tr>
+<tr>
<td>Cygwin/Win32</td>
<td>x86<sup><a href="#pf_1">1</a></sup></td>
<td>GCC 3.4.X, binutils 2.15</td>
@@ -617,18 +623,18 @@
<dt><tt>cfrontend-x.y.source.tar.gz</tt></dt>
<dd>Source release of the GCC front end.<br/></dd>
- <dt><tt>cfrontend-x.y.sparc-sun-solaris2.8.tar.gz</tt></dt>
- <dd>Binary release of the GCC front end for Solaris/Sparc.
- <br/></dd>
-
<dt><tt>cfrontend-x.y.i686-redhat-linux-gnu.tar.gz</tt></dt>
<dd>Binary release of the GCC front end for Linux/x86.<br/></dd>
- <dt><tt>cfrontend-x.y.i386-unknown-freebsd5.1.tar.gz</tt></dt>
- <dd>Binary release of the GCC front end for FreeBSD/x86.<br/></dd>
+ <dt><tt>llvm-gcc4-x.y.source.tar.gz</tt></dt>
+ <dd>Source release of the llvm-gcc4 front end. See README.LLVM in the root
+ directory for build instructions.<br/></dd>
+
+ <dt><tt>llvm-gcc4-x.y.powerpc-apple-darwin8.6.0.tar.gz</tt></dt>
+ <dd>Binary release of the llvm-gcc4 front end for MacOS X/PowerPC.<br/></dd>
- <dt><tt>cfrontend-x.y.powerpc-apple-darwin7.8.0.tar.gz</tt></dt>
- <dd>Binary release of the GCC front end for MacOS X/PPC.<br/></dd>
+ <dt><tt>llvm-gcc4-x.y.i686-apple-darwin8.6.1.tar.gz</tt></dt>
+ <dd>Binary release of the llvm-gcc4 front end for MacOS X/X86.<br/></dd>
</dl>
</div>
@@ -661,6 +667,7 @@
labels:</p>
<ul>
+<li>Release 1.7: <b>RELEASE_17</b></li>
<li>Release 1.6: <b>RELEASE_16</b></li>
<li>Release 1.5: <b>RELEASE_15</b></li>
<li>Release 1.4: <b>RELEASE_14</b></li>
@@ -680,8 +687,7 @@
configured by the LLVM configure script as well as automatically updated when
you run <tt>cvs update</tt>.</p>
-<p>If you would like to get the GCC front end source code, you can also get it
-from the CVS repository:</p>
+<p>If you would like to get the GCC 3.4 front end source code, you can also get it from the CVS repository:</p>
<pre>
cvs -z3 -d :pserver:anon at llvm-cvs.cs.uiuc.edu:/var/cvs/llvm co llvm-gcc
@@ -693,22 +699,6 @@
</div>
<!-- ======================================================================= -->
-<div class="doc_subsubsection">
- <a name="mirrors">LLVM CVS Mirrors</a>
-</div>
-
-<div class="doc_text">
-
-<p>If the main CVS server is overloaded or inaccessible, you can try one of
-these user-hosted mirrors:</p>
-
-<ul>
-<li><a href="http://llvm.x10sys.com/">Mirror hosted by eXtensible Systems
-Inc.</a></li>
-</ul>
-</div>
-
-<!-- ======================================================================= -->
<div class="doc_subsection">
<a name="installcf">Install the GCC Front End</a>
</div>
@@ -1551,7 +1541,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.org">The LLVM Compiler Infrastructure</a><br>
- Last modified: $Date: 2006/04/09 23:45:37 $
+ Last modified: $Date: 2006/04/20 05:09:16 $
</address>
</body>
</html>
Index: llvm/docs/GettingStartedVS.html
diff -u llvm/docs/GettingStartedVS.html:1.6 llvm/docs/GettingStartedVS.html:1.6.2.1
--- llvm/docs/GettingStartedVS.html:1.6 Mon Mar 13 23:39:39 2006
+++ llvm/docs/GettingStartedVS.html Thu Apr 20 00:09:16 2006
@@ -99,7 +99,7 @@
<li><tt>cd llvm</tt></li>
</ol></li>
- <li>With anonymous CVS access (or use a <a href="#mirror">mirror</a>):
+ <li>With anonymous CVS access:
<ol>
<li><tt>cd <i>where-you-want-llvm-to-live</i></tt></li>
<li><tt>cvs -d
@@ -347,7 +347,7 @@
<a href="mailto:jeffc at jolt-lang.org">Jeff Cohen</a><br>
<a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
- Last modified: $Date: 2006/03/14 05:39:39 $
+ Last modified: $Date: 2006/04/20 05:09:16 $
</address>
</body>
</html>
Index: llvm/docs/ReleaseNotes.html
diff -u llvm/docs/ReleaseNotes.html:1.347 llvm/docs/ReleaseNotes.html:1.347.2.1
--- llvm/docs/ReleaseNotes.html:1.347 Thu Mar 2 18:34:26 2006
+++ llvm/docs/ReleaseNotes.html Thu Apr 20 00:09:16 2006
@@ -4,7 +4,7 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" href="llvm.css" type="text/css">
- <title>LLVM 1.7cvs Release Notes</title>
+ <title>LLVM 1.7 Release Notes</title>
</head>
<body>
@@ -60,38 +60,218 @@
<div class="doc_text">
-<p>This is the seventh public release of the LLVM Compiler Infrastructure. This
-release incorporates a large number of enhancements and additions (primarily in
-the code generator), which combine to improve the quality of the code generated
-by LLVM by up to 30% in some cases. This release is also the first release to
-have first-class support for Mac OS X: all of the major bugs have been shaken
-out and it is now as well supported as Linux on X86.</p>
+<p>This is the eighth public release of the LLVM Compiler Infrastructure. This
+release incorporates a large number of enhancements and new features,
+including vector support (Intel SSE and Altivec), a new GCC4.0-based
+C/C++ front-end, Objective C/C++ support, inline assembly support, and many
+other big features.
+</p>
</div>
<!--=========================================================================-->
<div class="doc_subsection">
-<a name="newfeatures">New Features in LLVM 1.7cvs</a>
+<a name="newfeatures">New Features in LLVM 1.7</a>
</div>
+<!--_________________________________________________________________________-->
+<div class="doc_subsubsection"><a name="llvmgcc4">GCC4.0-based llvm-gcc
+front-end</a></div>
+
+<div class="doc_text">
+
+<p>LLVM 1.7 includes a brand new llvm-gcc, based on GCC 4.0.1. This version
+of llvm-gcc solves many serious long-standing problems with llvm-gcc, including
+all of those blocked by the <a href="http://llvm.org/PR498">llvm-gcc 4 meta
+bug</a>. In addition, llvm-gcc4 implements support for many new features,
+including GCC inline assembly, generic vector support, SSE and Altivec
+intrinsics, and several new GCC attributes. Finally, llvm-gcc4 is
+significantly faster than llvm-gcc3, respects -O options, its -c/-S options
+correspond to GCC's (they emit native code), supports Objective C/C++, and
+it has debugging support well underway.</p>
+
+<p>If you can use it, llvm-gcc4 offers significant new functionality, and we
+hope that it will replace llvm-gcc3 completely in a future release.
+Unfortunately, it does not currently support C++ exception handling at all, and
+it only works on Apple Mac OS/X machines with X86 or PowerPC processors.
+</p>
+
+</div>
+
+<!--_________________________________________________________________________-->
+<div class="doc_subsubsection"><a name="inlineasm">Inline Assembly
+Support</a></div>
+
+<div class="doc_text">
+
+<p>The LLVM IR and llvm-gcc4 front-end now fully support arbitrary GCC <a
+href="LangRef.html#inlineasm">inline assembly</a>. The LLVM X86 and PowerPC
+code generators have initial support for it,
+being able to compile basic statements, but are missing some features. Please
+report any inline asm statements that crash the compiler or that are miscompiled
+as bugs.</p>
+
+</div>
+
+<!--_________________________________________________________________________-->
+<div class="doc_subsubsection"><a name="newsparc">New SPARC backend</a></div>
+
+<div class="doc_text">
+
+<p>LLVM 1.7 includes a new, fully functional, SPARC backend built in the
+target-independent code generator. This SPARC backend includes support for
+SPARC V8 and SPARC V9 subtargets (controlling whether V9 features can be used),
+and targets the 32-bit SPARC ABI.</p>
+
+<p>The LLVM 1.7 release is the last release that will include the LLVM "SparcV9"
+backend, which was the very first LLVM native code generator. It will
+be removed in LLVM 1.8, being replaced with the new SPARC backend.</p>
+
+</div>
+
+<!--_________________________________________________________________________-->
+<div class="doc_subsubsection"><a name="genvector">Generic Vector Support
+</a></div>
+
+<div class="doc_text">
+
+<p>LLVM now includes significantly extended support for SIMD vectors in its
+core instruction set. It now includes three new instructions for manipulating
+vectors: <a href="LangRef.html#i_extractelement"><tt>extractelement</tt></a>,
+<a href="LangRef.html#i_insertelement"><tt>insertelement</tt></a>, and
+<a href="LangRef.html#i_shufflevector"><tt>shufflevector</tt></a>. Further,
+many bugs in vector handling have been fixed, and vectors are now supported by
+the target-independent code generator. For example, if a vector operation is
+not supported by a particular target, it will be correctly broken down and
+executed as scalar operations.</p>
+
+<p>Because llvm-gcc3 does not support GCC generic vectors or vector intrinsics,
+llvm-gcc4 must be used.</p>
+</div>
+
+
+<!--_________________________________________________________________________-->
+<div class="doc_subsubsection"><a name="ssealtivec">Intel SSE and PowerPC
+Altivec support
+</a></div>
+
+<div class="doc_text">
+
+<p>The LLVM X86 backend now supports Intel SSE 1, 2, and 3, and now uses scalar
+SSE operations to implement scalar floating point math when the target supports
+SSE1 (for floats) or SSE2 (for doubles). Vector SSE instructions are generated
+by llvm-gcc4 when the generic vector mechanism or specific SSE intrinsics are
+used.
+</p>
+
+<p>The LLVM PowerPC backend now supports the Altivec instruction set, including
+both GCC -maltivec and -faltivec modes. Altivec instructions are generated
+by llvm-gcc4 when the generic vector mechanism or specific Altivec intrinsics
+are used.
+</p>
+
+</div>
+
+<!--_________________________________________________________________________-->
+<div class="doc_subsubsection"><a name="optimizernew">Optimizer
+Improvements</a></div>
+
+<div class="doc_text">
+<ul>
+<li>The Loop Unswitching pass (<tt>-loop-unswitch</tt>) has had several bugs
+ fixed, has several new features, and is enabled by default in llvmgcc3
+ now.</li>
+<li>The Loop Strength Reduction pass (<tt>-loop-reduce</tt>) is now enabled for
+ the X86 and Alpha backends.</li>
+<li>The Instruction Combining pass (<tt>-instcombine</tt>) now includes a
+ framework and implementation for simplifying code based on whether computed
+ bits are demanded or not.</li>
+<li>The Scalar Replacement of Aggregates pass (<tt>-scalarrepl</tt>) can now
+ promote simple unions to registers.</li>
+<li>The Reassociation pass (<tt>-reassociate</tt>) can now
+ factor expressions, e.g. turning "A*A+A*B" into "A*(A+B)".</li>
+<li>Several LLVM passes are <a href="http://llvm.org/PR681">significantly
+faster</a>.</li>
+</ul>
+</div>
+
+<!--_________________________________________________________________________-->
+<div class="doc_subsubsection"><a name="codgennew">Code Generator
+Improvements</a></div>
+
<div class="doc_text">
<ul>
-<li>New C front-end.</li>
-<li>New SPARC backend.</li>
-<li>Inline assembly support.</li>
+<li>LLVM has a new prepass (before register allocation) list scheduler, which
+ supports bottom-up and top-down scheduling, pluggable priority functions and
+ pluggable hazard recognizers. The X86 backend uses this to reduce register
+ pressure and RISC targets schedule based on operation latency.</li>
+<li>The tblgen-based target description framework introduced in LLVM 1.6 has
+ several new features, useful for targets that can fold loads and stores into
+ operations, and features that make the .td files more expressive.</li>
+<li>The instruction selector is significantly faster in 1.7 than in 1.6.</li>
+<li>The X86, Alpha and Itanium backends use new DAG-DAG instruction selectors,
+ making them easier to maintain and generate slightly better code.</li>
+<li>The X86 backend now supports generation of Scalar SSE code for scalar FP
+ expressions. LLVM provides significantly better performance with Scalar SSE
+ instructions than it does with the Intel floating point stack
+ instructions.</li>
+<li>The Itanium backend now has a bundling pass, which improves performance
+ by ~10% and reduces code size (previously it unconditionally inserted a stop
+ bit after every instruction).</li>
</ul>
</div>
+<!--_________________________________________________________________________-->
+<div class="doc_subsubsection"><a name="othernew">Other New Features</a></div>
+
+<div class="doc_text">
+<ul>
+<li>The Mac OS/X PowerPC and X86 backends now have initial support for
+ Darwin DWARF
+ debugging information, however, debug info generation has been disabled for
+ the 1.7 release in llvmgcc4.</li>
+<li>LLVM includes the new <a href="docs/CommandGuide/html/llvm-config.html">
+ llvm-config</a> utility, which makes it easier to build and link programs
+ against the LLVM libraries when not using the LLVM makefiles.</li>
+<li>LLVM now supports first class global ctor/dtor initialization lists, no
+ longer forcing targets to use "__main".</li>
+<li>LLVM supports assigning globals and functions to a particular section
+ in the result executable using the GCC section attribute.</li>
+<li><a href="ExtendingLLVM.html">Adding intrinsics to LLVM</a> is now
+ significantly easier.</li>
+<li>llvmgcc4 now fully supports C99 Variable Length Arrays, including dynamic
+ stack deallocation.</li>
+
+</ul>
+</div>
+
+
<!--=========================================================================-->
<div class="doc_subsection">
-<a name="changes">Significant changes in LLVM 1.7cvs</a>
+<a name="changes">Significant Changes in LLVM 1.7</a>
</div>
<div class="doc_text">
<ul>
-<li>Removed the llvm.readport/llvm.writeport/llvm.readio/llvm.writeio
- intrinsics.</li>
-<li>Separated the other intrinsics based on type.</li>
+<li>The official LLVM URL is now <a href="http://llvm.org/">
+ http://llvm.org/</a>.</li>
+<li>The LLVM intrinsics used to be overloaded based on type: for example,
+ <a href="LangRef.html#int_ctpop"><tt>llvm.ctpop</tt></a> could work with any
+ integer datatype. They are now separated into different intrinsics with
+ suffixes to denote their argument type (e.g. <tt>llvm.ctpop.i32</tt>)). Old
+ LLVM .ll and .bc files that use these intrinsics will continue to work with
+ new LLVM versions (they are transparently upgraded by the parsers), but will
+ cause a warning to be emitted.</li>
+<li>The <tt>llvm.readport</tt>, <tt>llvm.writeport</tt>, <tt>llvm.readio</tt>,
+ and <tt>llvm.writeio</tt> intrinsics have been removed. The first two
+ were ever only supported by the X86 backend, the last two were never
+ correctly supported by any target, and none were accessible through the
+ C front-end. Inline assembly support can now be used to
+ implement these operations.</li>
+<li>The <tt>llvm-db</tt> tool had basic support for stepping through code, which
+ used the JIT. This code has been removed, and DWARF emission support added
+ instead. <tt>llvm-db</tt> still exists in CVS if someone wanted to write a
+ <tt>ptrace</tt> backend for it.</li>
</ul>
</div>
@@ -155,12 +335,12 @@
components, please contact us on the llvmdev list.</p>
<ul>
-<li>The following passes are incomplete or buggy, and may be removed in future
- releases: <tt>-cee</tt></li>
-<li>The <tt>llvm-db</tt> tool is in a very early stage of development, but can
- be used to step through programs and inspect the stack.</li>
+<li>The <tt>-cee</tt> pass is known to be buggy, and may be removed in in a
+ future release.</li>
<li>The IA64 code generator is experimental.</li>
<li>The Alpha JIT is experimental.</li>
+<li>"<tt>-filetype=asm</tt>" (the default) is the only supported value for the
+ <tt>-filetype</tt> llc option.</li>
</ul>
</div>
@@ -173,7 +353,7 @@
<div class="doc_text">
<ul>
- <li>The <a href="http://llvm.org/PR656">configure script sometimes fails on Solaris/Sparc</a>. A work around is documented in <a href="http://llvm.org/PR656">PR656.</a></li>
+<li>none yet</li>
</ul>
</div>
@@ -201,11 +381,14 @@
<div class="doc_text">
-These bugs are known for the old front-end. The new GCC-4-based C front-end
-suffers from none of these.
+<p>
+llvm-gcc3 has many significant problems that are fixed by llvm-gcc4. See
+ those blocked on the <a href="http://llvm.org/PR498">llvm-gcc4 meta bug</a>.
+Two major ones include:</p>
<ul>
-<li>C99 Variable sized arrays do not release stack memory when they go out of
+<li>With llvm-gcc3,
+ C99 variable sized arrays do not release stack memory when they go out of
scope. Thus, the following program may run out of stack space:
<pre>
for (i = 0; i != 1000000; ++i) {
@@ -214,7 +397,7 @@
}
</pre></li>
-<li>Initialization of global union variables can only be done <a
+<li>With llvm-gcc3, Initialization of global union variables can only be done <a
href="http://llvm.org/PR162">with the largest union member</a>.</li>
</ul>
@@ -398,11 +581,6 @@
<ul>
-<li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
-parser is significantly more standards compliant (and picky) than prior GCC
-versions. For more information, see the C++ section of the <a
-href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
-
<li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
function and in the <tt>setjmp</tt> receiver function may not be run.
@@ -442,6 +620,12 @@
supported</a>. This should not affect LLVM produced by the C or C++
frontends.</li>
+<li>The C backend does not correctly implement the <a
+href="LangRef.html#i_stacksave"><tt>llvm.stacksave</tt></a> or
+<a href="LangRef.html#i_stackrestore"><tt>llvm.stackrestore</tt></a>
+intrinsics. This means that some code compiled by it can run out of stack
+space if they depend on these (e.g. C99 varargs).</li>
+
</ul>
</div>
@@ -454,7 +638,8 @@
<div class="doc_text">
<ul>
-<li>None yet</li>
+<li><a href="http://llvm.org/PR736">Indirect calls crash JIT on
+Darwin/x86</a>.</li>
</ul>
</div>
@@ -467,21 +652,8 @@
<div class="doc_text">
<ul>
-<li>None yet</li>
-</ul>
-
-</div>
-
-<!-- ======================================================================= -->
-<div class="doc_subsection">
- <a name="sparcv9-be">Known problems with the SparcV9 back-end</a>
-</div>
-
-<div class="doc_text">
-
-<ul>
-<li><a href="http://llvm.org/PR60">[sparcv9] SparcV9 backend miscompiles
-several programs in the LLVM test suite</a></li>
+<li><a href="http://llvm.org/PR642">PowerPC backend does not correctly
+implement ordered FP comparisons</a>.</li>
</ul>
</div>
@@ -534,14 +706,33 @@
<!-- ======================================================================= -->
<div class="doc_subsection">
- <a name="sparc">Known problems with the SPARC back-end</a>
+ <a name="sparc-be">Known problems with the SPARC back-end</a>
+</div>
+
+<div class="doc_text">
+
+<ul>
+<li>The SPARC backend only supports the 32-bit SPARC ABI (-m32), it does not
+ support the 64-bit SPARC ABI (-m64).</li>
+</ul>
+
+</div>
+
+
+<!-- ======================================================================= -->
+<div class="doc_subsection">
+ <a name="sparcv9-be">Known problems with the SparcV9 back-end</a>
</div>
<div class="doc_text">
<ul>
-<li>None yet.</li>
+<li><a href="http://llvm.org/PR60">[sparcv9] SparcV9 backend miscompiles
+several programs in the LLVM test suite</a></li>
+<li>The SparcV9 backend is slated to be removed before the LLVM 1.8
+ release.</li>
</ul>
+
</div>
<!-- *********************************************************************** -->
@@ -577,7 +768,7 @@
src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
<a href="http://llvm.org/">The LLVM Compiler Infrastructure</a><br>
- Last modified: $Date: 2006/03/03 00:34:26 $
+ Last modified: $Date: 2006/04/20 05:09:16 $
</address>
</body>
Index: llvm/docs/UsingLibraries.html
diff -u llvm/docs/UsingLibraries.html:1.19 llvm/docs/UsingLibraries.html:1.19.2.1
--- llvm/docs/UsingLibraries.html:1.19 Mon Mar 13 23:39:39 2006
+++ llvm/docs/UsingLibraries.html Thu Apr 20 00:09:17 2006
@@ -23,6 +23,8 @@
<p>Written by <a href="mailto:rspencer at x10sys.com">Reid Spencer</a></p>
</div>
+<p class="doc_warning">Warning: This document is out of date, please see <a href="CommandGuide/html/llvm-config.html">llvm-config</a> for more information.</p>
+
<!-- ======================================================================= -->
<div class="doc_section"><a name="abstract">Abstract</a></div>
<div class="doc_text">
@@ -497,7 +499,7 @@
<a href="mailto:rspencer at x10sys.com">Reid Spencer</a>
</address>
<a href="http://llvm.org">The LLVM Compiler Infrastructure</a>
-<br>Last modified: $Date: 2006/03/14 05:39:39 $ </div>
+<br>Last modified: $Date: 2006/04/20 05:09:17 $ </div>
</body>
</html>
<!-- vim: sw=2 ts=2 ai
More information about the llvm-commits
mailing list