RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2025-02-24 21:00:36 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

* Use stylesheets

Browse Source 
* Close <li>, <a>, and <p> tags


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@10149 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Misha Brukman 2003-11-22 00:38:41 +00:00
parent a59f41fc6c
commit 500bc30595
1 changed files with 301 additions and 187 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

488
docs/ReleaseNotes.html
View File

@ -1,16 +1,21 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
<html><head><title>LLVM 1.1 Release Notes</title></head> "http://www.w3.org/TR/html4/strict.dtd">
<body bgcolor=white> <html>
<head>
<link rel="stylesheet" href="llvm.css" type="text/css">
<title>LLVM 1.1 Release Notes</title>
</head>
<body>
<table width="100%" bgcolor="#330077" border=0 cellpadding=4 cellspacing=0> <div class="doc_title">
<tr><td>&nbsp; <font size=+3 color="#EEEEFF" face="Georgia,Palatino,Times,Roman"><b>LLVM 1.1 Release Notes</b></font></td> LLVM 1.1 Release Notes
</tr></table> </div>
<ol> <ol>
<li><a href="#intro">Introduction</a> <li><a href="#intro">Introduction</a></li>
<li><a href="#whatsnew">What's New?</a> <li><a href="#whatsnew">What's New?</a></li>
<li><a href="#portability">Portability and Supported Platforms</a> <li><a href="#portability">Portability and Supported Platforms</a></li>
<li><a href="#install-instructions">Installation Instructions</a> <li><a href="#install-instructions">Installation Instructions</a></li>
<li><a href="#knownproblems">Known Problems</a> <li><a href="#knownproblems">Known Problems</a>
<ul> <ul>
<!-- <li><a href="#portabilityprobs">Portability Problems</a> --> <!-- <li><a href="#portabilityprobs">Portability Problems</a> -->
@ -20,67 +25,73 @@
<li><a href="#x86-be">Known problems with the X86 Back-end</a> <li><a href="#x86-be">Known problems with the X86 Back-end</a>
<li><a href="#sparc-be">Known problems with the Sparc Back-end</a> <li><a href="#sparc-be">Known problems with the Sparc Back-end</a>
<li><a href="#c-be">Known problems with the C back-end</a> <li><a href="#c-be">Known problems with the C back-end</a>
</ul> </ul></li>
<li><a href="#additionalinfo">Additional Information</a> <li><a href="#additionalinfo">Additional Information</a></li>
</ul> </ul></li>
<p><b>Written by <a href="mailto:sabre@nondot.org">Chris Lattner</a></b><p>
</ol> </ol>
<div section="doc_text">
<p><b>Written by <a href="mailto:sabre@nondot.org">Chris Lattner</a></b><p>
</div>
<!-- *********************************************************************** --> <!-- *********************************************************************** -->
<table width="100%" bgcolor="#330077" border=0 cellpadding=4 cellspacing=0> <div class="doc_section">
<tr><td align=center><font color="#EEEEFF" size=+2 face="Georgia,Palatino"><b> <a name="intro">Introduction</a>
<a name="intro">Introduction </div>
</b></font></td></tr></table><ul>
<!-- *********************************************************************** --> <!-- *********************************************************************** -->
This document contains the release notes for the LLVM compiler infrastructure, <div class="doc_text">
release 1.1. Here we describe the status of LLVM, including any known problems,
and bug fixes from the previous release. The most up-to-date version of this <p>This document contains the release notes for the LLVM compiler
document can be found on the <a infrastructure, release 1.1. Here we describe the status of LLVM, including any
known problems, and bug fixes from the previous release. The most up-to-date
version of this document can be found on the <a
href="http://llvm.cs.uiuc.edu/releases/1.1/">LLVM 1.1 web site</a>. If you are href="http://llvm.cs.uiuc.edu/releases/1.1/">LLVM 1.1 web site</a>. If you are
not reading this on the LLVM web pages, you should probably go there, because not reading this on the LLVM web pages, you should probably go there, because
this document may be updated after the release.<p> this document may be updated after the release.</p>
For more information about LLVM, including information about potentially more <p>For more information about LLVM, including information about potentially more
current releases, please check out the <a href="http://llvm.cs.uiuc.edu">main current releases, please check out the <a href="http://llvm.cs.uiuc.edu">main
web site</a>. If you have questions or comments, the <a web site</a>. If you have questions or comments, the <a
href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM developer's mailing href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM developer's mailing
list</a> is a good place to send them.<p> list</a> is a good place to send them.</p>
Note that if you are reading this file from CVS, that this document applies to <p>Note that if you are reading this file from CVS, that this document applies
the <i>next</i> release, not the previous one. To see the release notes for the to the <i>next</i> release, not the previous one. To see the release notes for
previous release, see the <a href="http://llvm.cs.uiuc.edu/releases/">releases the previous release, see the <a
page</a>.<p> href="http://llvm.cs.uiuc.edu/releases/">releases page</a>.</p>
</div>
<!-- *********************************************************************** --> <!-- *********************************************************************** -->
</ul><table width="100%" bgcolor="#330077" border=0 cellpadding=4 cellspacing=0> <div class="doc_section">
<tr><td align=center><font color="#EEEEFF" size=+2 face="Georgia,Palatino"><b> <a name="whatsnew">What's New?</a>
<a name="whatsnew">What's New? </div>
</b></font></td></tr></table><ul>
<!-- *********************************************************************** --> <!-- *********************************************************************** -->
This is the second public release of the LLVM compiler infrastructure. This <div class="doc_text">
release implements the following new features:<p>
<p>This is the second public release of the LLVM compiler infrastructure. This
release implements the following new features:</p>
<ol> <ol>
<p><li><a <li><a
href="http://mail.cs.uiuc.edu/pipermail/llvmdev/2003-November/000528.html">A new href="http://mail.cs.uiuc.edu/pipermail/llvmdev/2003-November/000528.html">A new
LLVM profiler, similar to gprof</a> is available</li></p> LLVM profiler, similar to gprof</a> is available</li>
<p><li>LLVM and the C/C++ front-end now compile on Mac OSX! Mac OSX users can <li>LLVM and the C/C++ front-end now compile on Mac OSX! Mac OSX users can
now explore the LLVM optimizer with the C backend (note that LLVM requires GCC now explore the LLVM optimizer with the C backend (note that LLVM requires GCC
3.3 on Mac OSX).</li></p> 3.3 on Mac OSX).</li>
<p><li>LLVM has been <a <li>LLVM has been <a
href="http://mail.cs.uiuc.edu/pipermail/llvmdev/2003-November/000554.html">moved href="http://mail.cs.uiuc.edu/pipermail/llvmdev/2003-November/000554.html">moved
into an 'llvm' C++ namespace</a>, for easier integration with third-party into an 'llvm' C++ namespace</a>, for easier integration with third-party
code.</a> Note that due to a bug in GDB 5.x, to debug namespacified LLVM code, code.</a> Note that due to a bug in GDB 5.x, to debug namespacified LLVM code,
you will need to upgrade to GDB 6.</li></p> you will need to upgrade to GDB 6.</li>
</ol> </ol>
In this release, the following missing features were implemented:<p> <p>In this release, the following missing features were implemented:</p>
<ol> <ol>
<li><a href="http://llvm.cs.uiuc.edu/PR88">The interpreter does not support <li><a href="http://llvm.cs.uiuc.edu/PR88">The interpreter does not support
@ -92,9 +103,10 @@ invoke or unwind</a></li>
<li><a href="http://llvm.cs.uiuc.edu/PR117">llvm-nm cannot read archive <li><a href="http://llvm.cs.uiuc.edu/PR117">llvm-nm cannot read archive
files</a></li> files</a></li>
</ol><p> </ol>
In this release, the following Quality of Implementation issues were fixed:<p> <p>In this release, the following Quality of Implementation issues were
fixed:</p>
<ol> <ol>
@ -109,15 +121,13 @@ build problems</a></li>
<li><a href="http://llvm.cs.uiuc.edu/PR114">LLVM header files should be -Wold-style-cast clean</a></li> <li><a href="http://llvm.cs.uiuc.edu/PR114">LLVM header files should be -Wold-style-cast clean</a></li>
<li>The LLVM bytecode reader has been <a <li>The LLVM bytecode reader has been <a
href="http://llvm.cs.uiuc.edu/PR127">sped up a lot</a> (up to 4x in some href="http://llvm.cs.uiuc.edu/PR127">sped up a lot</a> (up to 4x in some
cases).</li> cases).</li>
</ol><p> </ol>
<p>In this release, the following bugs in the previous release were fixed:</p>
In this release, the following bugs in the previous release were fixed:<p>
<ol> <ol>
<li><a href="http://llvm.cs.uiuc.edu/PR57">[inliner] Inlining invoke with PHI in unwind target is broken</a></li> <li><a href="http://llvm.cs.uiuc.edu/PR57">[inliner] Inlining invoke with PHI in unwind target is broken</a></li>
@ -136,7 +146,7 @@ In this release, the following bugs in the previous release were fixed:<p>
<li><a href="http://llvm.cs.uiuc.edu/PR72">[build problem] Callgraph.cpp not pulled in from libipa.a</a></li> <li><a href="http://llvm.cs.uiuc.edu/PR72">[build problem] Callgraph.cpp not pulled in from libipa.a</a></li>
<li><a href="http://llvm.cs.uiuc.edu/PR77">Variables in scope of output setjmp <li><a href="http://llvm.cs.uiuc.edu/PR77">Variables in scope of output setjmp
calls should be volatile</a>. Note that this does not effect correctness on calls should be volatile</a>. Note that this does not effect correctness on
many platforms, such as X86. many platforms, such as X86.</li>
<li><a href="http://llvm.cs.uiuc.edu/PR79">llvm-gcc crashes compiling global union initializer</a></li> <li><a href="http://llvm.cs.uiuc.edu/PR79">llvm-gcc crashes compiling global union initializer</a></li>
<li><a href="http://llvm.cs.uiuc.edu/PR80">C front-end crash on empty structure</a></li> <li><a href="http://llvm.cs.uiuc.edu/PR80">C front-end crash on empty structure</a></li>
<li><a href="http://llvm.cs.uiuc.edu/PR81">CFrontend crashes when compiling C99 compound expressions</a></li> <li><a href="http://llvm.cs.uiuc.edu/PR81">CFrontend crashes when compiling C99 compound expressions</a></li>
@ -164,7 +174,7 @@ many platforms, such as X86.
<li><a href="http://llvm.cs.uiuc.edu/PR130">[vmcore] Symbol table doesn't rename colliding variables during type resolution</a></li> <li><a href="http://llvm.cs.uiuc.edu/PR130">[vmcore] Symbol table doesn't rename colliding variables during type resolution</a></li>
<li><a href="http://llvm.cs.uiuc.edu/PR131">[llvm-gcc] ?: operator as lvalue not implemented</a></li> <li><a href="http://llvm.cs.uiuc.edu/PR131">[llvm-gcc] ?: operator as lvalue not implemented</a></li>
<li><a href="http://llvm.cs.uiuc.edu/PR133">[C/C++] Bogus warning about taking the address of 'register' variable</a></li> <li><a href="http://llvm.cs.uiuc.edu/PR133">[C/C++] Bogus warning about taking the address of 'register' variable</a></li>
<li><a href="http://llvm.cs.uiuc.edu/PR97">bugpoint must not pass -R<directory> to Mach-O linker</a></li> <li><a href="http://llvm.cs.uiuc.edu/PR97">bugpoint must not pass -R&lt;directory&gt; to Mach-O linker</a></li>
<li><a href="http://llvm.cs.uiuc.edu/PR113">crash assigning into an array in a struct which contains a bitfield</a>.</li> <li><a href="http://llvm.cs.uiuc.edu/PR113">crash assigning into an array in a struct which contains a bitfield</a>.</li>
<li><a href="http://llvm.cs.uiuc.edu/PR6">Oversized integer bitfields cause crash</a></li> <li><a href="http://llvm.cs.uiuc.edu/PR6">Oversized integer bitfields cause crash</a></li>
<li><a href="http://llvm.cs.uiuc.edu/PR140">gccld produces a runner script that includes command-line options to load the necessary shared objects</a></li> <li><a href="http://llvm.cs.uiuc.edu/PR140">gccld produces a runner script that includes command-line options to load the necessary shared objects</a></li>
@ -173,41 +183,46 @@ many platforms, such as X86.
<li><a href="http://llvm.cs.uiuc.edu/PR143">[llvm-gcc] Illegal union field reference</a></li> <li><a href="http://llvm.cs.uiuc.edu/PR143">[llvm-gcc] Illegal union field reference</a></li>
</ol><p> </ol><p>
At this time, LLVM is known to work properly with SPEC CPU 2000, the Olden <p>At this time, LLVM is known to work properly with SPEC CPU 2000 (X86 only),
benchmarks, and the Ptrdist benchmarks among many other programs. Note however the Olden benchmarks, and the Ptrdist benchmarks among many other programs.
that the Sparc and X86 backends do not currently support exception throwing or Note however that the Sparc and X86 backends do not currently support exception
long jumping (including 253.perlbmk in SPEC). For these programs you must use throwing or long jumping (including 253.perlbmk in SPEC). For these programs,
the C backend.<p> you must use the C backend.</p>
</div>
<!-- *********************************************************************** --> <!-- *********************************************************************** -->
</ul><table width="100%" bgcolor="#330077" border=0 cellpadding=4 cellspacing=0> <div class="doc_section">
<tr><td align=center><font color="#EEEEFF" size=+2 face="Georgia,Palatino"><b> <a name="portability">Portability and Supported Platforms</a>
<a name="portability">Portability and Supported Platforms </div>
</b></font></td></tr></table><ul>
<!-- *********************************************************************** --> <!-- *********************************************************************** -->
LLVM has been extensively tested on Intel and AMD machines running Red <div class="doc_text">
<p>LLVM has been extensively tested on Intel and AMD machines running Red
Hat Linux, and Sun UltraSPARC workstations running Solaris 8. Additionally, Hat Linux, and Sun UltraSPARC workstations running Solaris 8. Additionally,
LLVM works on Mac OS/X 10.3 and above, but only with the C back-end (no native LLVM works on Mac OS/X 10.3 and above, but only with the C back-end (no native
backend for the PowerPC is available yet). backend for the PowerPC is available yet).
The core LLVM infrastructure uses "autoconf" for portability, so hopefully we The core LLVM infrastructure uses "autoconf" for portability, so hopefully we
work on more platforms than that. However, it is likely that we work on more platforms than that. However, it is likely that we
missed something, and that minor porting is required to get LLVM to work on missed something, and that minor porting is required to get LLVM to work on
new platforms. We welcome portability patches and error messages.<p> new platforms. We welcome portability patches and error messages.</p>
</div>
<!-- *********************************************************************** --> <!-- *********************************************************************** -->
</ul><table width="100%" bgcolor="#330077" border=0 cellpadding=4 cellspacing=0> <div class="doc_section">
<tr><td align=center><font color="#EEEEFF" size=+2 face="Georgia,Palatino"><b> <a name="knownproblems">Known Problems</a>
<a name="knownproblems">Known Problems </div>
</b></font></td></tr></table><ul>
<!-- *********************************************************************** --> <!-- *********************************************************************** -->
This section contains all known problems with the LLVM system, listed by <div class="doc_text">
<p>This section contains all known problems with the LLVM system, listed by
component. As new problems are discovered, they will be added to these component. As new problems are discovered, they will be added to these
sections. sections.</p>
</div>
<!-- _______________________________________________________________________ --> <!-- _______________________________________________________________________ -->
<!-- <!--
@ -215,27 +230,47 @@ sections.
--> -->
<!-- _______________________________________________________________________ --> <!-- ======================================================================= -->
</ul><h4><a name="core"><hr size=0>Known problems with the LLVM Core</h4><ul> <div class="doc_subsection">
<a name="core">Known problems with the LLVM Core</a>
</div>
<li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not work.<p> <div class="doc_text">
<ul>
<li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not
work.</li>
<li>The JIT does not use mutexes to protect its internal data structures. As <li>The JIT does not use mutexes to protect its internal data structures. As
such, execution of a threaded program could cause these data structures to such, execution of a threaded program could cause these data structures to be
be corrupted.<p> corrupted.</li>
<li>It is not possible to <tt>dlopen</tt> an LLVM bytecode file in the JIT.<p> <li>It is not possible to <tt>dlopen</tt> an LLVM bytecode file in the JIT.</li>
<li>Linking in static archive files (.a files) is very slow (there is no symbol <li>Linking in static archive files (.a files) is very slow (there is no symbol
table in the archive).<p> table in the archive).</li>
<li><a href="http://llvm.cs.uiuc.edu/PR82">LLVM cannot handle structures with <li><a href="http://llvm.cs.uiuc.edu/PR82">LLVM cannot handle structures with
more than 256 elements</a>.<p> more than 256 elements</a>.</li>
</ul>
</div>
<!-- ======================================================================= -->
<div class="doc_subsection">
<a name="c-fe">Known problems with the C front-end</a>
</div>
<!-- _______________________________________________________________________ --> <!-- _______________________________________________________________________ -->
</ul><h4><a name="c-fe"><hr size=0>Known problems with the C front-end</h4><ul> <div class="doc_subsubsection">
Bugs
</div>
</ul><b>Bugs:</b><ul><p> <div class="doc_text">
<ul>
<li>C99 Variable sized arrays do not release stack memory when they go out of <li>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: scope. Thus, the following program may run out of stack space:
@ -244,139 +279,187 @@ more than 256 elements</a>.<p>
int X[n]; int X[n];
foo(X); foo(X);
} }
</pre><p> </pre></li>
</ul><b>Notes:</b><ul><p> </ul>
<li>Inline assembly is not yet supported.<p> </div>
<!-- _______________________________________________________________________ -->
<div class="doc_subsubsection">
Notes
</div>
<div class="doc_text">
<ul>
<li>Inline assembly is not yet supported.</li>
<li>"long double" is transformed by the front-end into "double". There is no <li>"long double" is transformed by the front-end into "double". There is no
support for floating point data types of any size other than 32 and 64 bits. support for floating point data types of any size other than 32 and 64
<p> bits.</li>
<li>The following Unix system functionality has not been tested and may not work: <li>The following Unix system functionality has not been tested and may not
work:
<ol> <ol>
<li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
<tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly. <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
<li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt> <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
- These functions have not been tested. - These functions have not been tested.
</ol><p> </ol></li>
<li>Although many GCC extensions are supported, some are not. In particular, <li>Although many GCC extensions are supported, some are not. In particular,
the following extensions are known to <b>not be</b> supported: the following extensions are known to <b>not be</b> supported:
<ol> <ol>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Labels-as-Values.html#Labels%20as%20Values">Labels as Values</a>: Getting pointers to labels, and computed gotos. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Labels-as-Values.html#Labels%20as%20Values">Labels as Values</a>: Getting pointers to labels, and computed gotos.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Nested-Functions.html#Nested%20Functions">Nested Functions</a>: As in Algol and Pascal, lexical scoping of functions. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Nested-Functions.html#Nested%20Functions">Nested Functions</a>: As in Algol and Pascal, lexical scoping of functions.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html#Extended%20Asm">Extended Asm</a>: Assembler instructions with C expressions as operands. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html#Extended%20Asm">Extended Asm</a>: Assembler instructions with C expressions as operands.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Asm-Labels.html#Asm%20Labels">Asm Labels</a>: Specifying the assembler name to use for a C symbol. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Asm-Labels.html#Asm%20Labels">Asm Labels</a>: Specifying the assembler name to use for a C symbol.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Explicit-Reg-Vars.html#Explicit%20Reg%20Vars">Explicit Reg Vars</a>: Defining variables residing in specified registers. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Explicit-Reg-Vars.html#Explicit%20Reg%20Vars">Explicit Reg Vars</a>: Defining variables residing in specified registers.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Return-Address.html#Return%20Address">Return Address</a>: Getting the return or frame address of a function. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Return-Address.html#Return%20Address">Return Address</a>: Getting the return or frame address of a function.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Vector-Extensions.html#Vector%20Extensions">Vector Extensions</a>: Using vector instructions through built-in functions. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Vector-Extensions.html#Vector%20Extensions">Vector Extensions</a>: Using vector instructions through built-in functions.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Target-Builtins.html#Target%20Builtins">Target Builtins</a>: Built-in functions specific to particular targets. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Target-Builtins.html#Target%20Builtins">Target Builtins</a>: Built-in functions specific to particular targets.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread-Local.html#Thread-Local">Thread-Local</a>: Per-thread variables. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread-Local.html#Thread-Local">Thread-Local</a>: Per-thread variables.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
</ol><p> </ol></li>
The following GCC extensions are <b>partially</b> supported. An ignored <p>The following GCC extensions are <b>partially</b> supported. An ignored
attribute means that the LLVM compiler ignores the presence of the attribute, attribute means that the LLVM compiler ignores the presence of the attribute,
but the code should still work. An unsupported attribute is one which is but the code should still work. An unsupported attribute is one which is
ignored by the LLVM compiler, which will cause a different interpretation of ignored by the LLVM compiler, which will cause a different interpretation of
the program.<p> the program.</p>
<ol> <ol>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>: <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
Arrays whose length is computed at run time.<br> Arrays whose length is computed at run time.<br>
Supported, but allocated stack space is not freed until the function returns (noted above). Supported, but allocated stack space is not freed until the function returns (noted above).</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>: <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
Declaring that functions have no side effects, or that they can never return.<br>
<b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>, <tt>constructor</tt>, <tt>destructor</tt>, <tt>unused</tt>, <tt>deprecated</tt>, Declaring that functions have no side effects, or that they can never
<tt>warn_unused_result</tt>, <tt>weak</tt><br> return.<br>
<b>Ignored:</b> <tt>noreturn</tt>, <tt>noinline</tt>, <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>, <tt>malloc</tt>
<tt>no_instrument_function</tt>, <tt>cdecl</tt><br> <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
<b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>, <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>, <tt>constructor</tt>, <tt>destructor</tt>, <tt>unused</tt>,
<tt>fastcall</tt>, all other target specific attributes <tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
<b>Ignored:</b> <tt>noreturn</tt>, <tt>noinline</tt>,
<tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
<tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
<b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>,
<tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
<tt>fastcall</tt>, all other target specific attributes</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>: <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
Specifying attributes of variables.<br> Specifying attributes of variables.<br>
<b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>, <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
<tt>deprecated</tt>, <tt>transparent_union</tt>, <tt>deprecated</tt>, <tt>transparent_union</tt>,
<tt>unused</tt>, <tt>weak</tt><br> <tt>unused</tt>, <tt>weak</tt><br>
<b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>, <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
<tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>, <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
<tt>vector_size</tt>, <tt>dllimport</tt>, <tt>vector_size</tt>, <tt>dllimport</tt>,
<tt>dllexport</tt>, all target specific attributes.<br> <tt>dllexport</tt>, all target specific attributes.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.
<b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>, <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
<tt>deprecated</tt>, <tt>may_alias</tt> <tt>deprecated</tt>, <tt>may_alias</tt>
<b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>
all target specific attributes.<br> <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
all target specific attributes.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>: <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
Other built-in functions.<br> Other built-in functions.<br>
We support all builtins which have a C language equivalent (e.g., We support all builtins which have a C language equivalent (e.g.,
<tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>, <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
<tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>, <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
<tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt> (ignored). <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt> (ignored).</li>
</ol><p>
</ol>
<p>The following extensions <b>are</b> known to be supported:</p>
The following extensions <b>are</b> known to be supported:
<ol> <ol>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Typeof.html#Typeof">Typeof</a>: <code>typeof</code>: referring to the type of an expression. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Typeof.html#Typeof">Typeof</a>: <code>typeof</code>: referring to the type of an expression.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Lvalues.html#Lvalues">Lvalues</a>: Using <code>?:</code>, "<code>,</code>" and casts in lvalues. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Lvalues.html#Lvalues">Lvalues</a>: Using <code>?:</code>, "<code>,</code>" and casts in lvalues.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variadic-Macros.html#Variadic%20Macros">Variadic Macros</a>: Macros with a variable number of arguments. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variadic-Macros.html#Variadic%20Macros">Variadic Macros</a>: Macros with a variable number of arguments.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Subscripting.html#Subscripting">Subscripting</a>: Any array can be subscripted, even if not an lvalue. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Subscripting.html#Subscripting">Subscripting</a>: Any array can be subscripted, even if not an lvalue.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pointer-Arith.html#Pointer%20Arith">Pointer Arith</a>:Arithmetic on <code>void</code>-pointers and function pointers. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pointer-Arith.html#Pointer%20Arith">Pointer Arith</a>:Arithmetic on <code>void</code>-pointers and function pointers.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions or arrays as values. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions or arrays as values.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers. <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Cast-to-Union.html#Cast%20to%20Union">Cast to Union</a>:Casting to union type from any member of the union.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/C---Comments.html#C++%20Comments">C++ Comments</a>: C++ comments are recognized.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Character-Escapes.html#Character%20Escapes">Character Escapes</a>: <code>\e</code> stands for the character &lt;ESC&gt;.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alternate-Keywords.html#Alternate%20Keywords">Alternate Keywords</a>:<code>__const__</code>, <code>__asm__</code>, etc., for header files.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Incomplete-Enums.html#Incomplete%20Enums">Incomplete Enums</a>: <code>enum foo;</code>, with details to follow.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Names.html#Function%20Names">Function Names</a>: Printable strings which are the name of the current function.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Unnamed-Fields.html#Unnamed%20Fields">Unnamed Fields</a>: Unnamed struct/union fields within structs/unions.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
</ol>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Cast-to-Union.html#Cast%20to%20Union">Cast to Union</a>:Casting to union type from any member of the union. <p>If you run into GCC extensions which have not been included in any of these
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such. lists, please let us know (also including whether or not they work).</p>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions. </div>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/C---Comments.html#C++%20Comments">C++ Comments</a>: C++ comments are recognized.
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Character-Escapes.html#Character%20Escapes">Character Escapes</a>: <code>\e</code> stands for the character &lt;ESC&gt;.
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alternate-Keywords.html#Alternate%20Keywords">Alternate Keywords</a>:<code>__const__</code>, <code>__asm__</code>, etc., for header files.
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Incomplete-Enums.html#Incomplete%20Enums">Incomplete Enums</a>: <code>enum foo;</code>, with details to follow.
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Names.html#Function%20Names">Function Names</a>: Printable strings which are the name of the current function.
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Unnamed-Fields.html#Unnamed%20Fields">Unnamed Fields</a>: Unnamed struct/union fields within structs/unions.
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.
</ol><p>
If you run into GCC extensions which have not been included in any of these <!-- ======================================================================= -->
lists, please let us know (also including whether or not they work). <div class="doc_subsection">
<a name="c++-fe">Known problems with the C++ front-end</a>
</div>
<div class="doc_text">
<p>For this release, the C++ front-end is considered to be fully functional but
of <b>beta</b> quality. It has been tested and works for a number of simple
programs that collectively exercise most of the language. Nevertheless, it has
not been in use as long as the C front-end. Please report any bugs or
problems.</p>
</div>
<!-- _______________________________________________________________________ --> <!-- _______________________________________________________________________ -->
</ul><h4><a name="c++-fe"><hr size=0>Known problems with the C++ front-end</h4><ul> <div class="doc_subsubsection">
Bugs
</div>
For this release, the C++ front-end is considered to be fully functional but <div class="doc_text">
of <b>beta</b> quality. It has been tested and works for a number of simple programs that collectively exercise most of the language. Nevertheless, it has not been in use as long as the C front-end. Please report any bugs or problems.<p>
</ul><b>Bugs</b>:<ul><p>
<ul>
<li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
front-end</a><p> front-end</a></li>
</ul>
</ul><b>Notes</b>:<ul><p> </div>
<!-- _______________________________________________________________________ -->
<div class="doc_subsubsection">
Notes
</div>
<div class="doc_text">
<ul>
<li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This <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 parser is significantly more standards compliant (and picky) than prior GCC
@ -387,7 +470,7 @@ href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.<p>
performed. In particular, destructors for objects in the <tt>longjmp</tt>ing 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. function and in the <tt>setjmp</tt> receiver function may not be run.
Objects in intervening stack frames will be destroyed however (which is Objects in intervening stack frames will be destroyed however (which is
better than most compilers).<p> better than most compilers).</li>
<li>The LLVM C++ front-end follows the <a <li>The LLVM C++ front-end follows the <a
href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>. href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
@ -398,79 +481,110 @@ href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.<p>
Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc). Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
<i>However</i>, the exception handling mechanism used by LLVM is very <i>However</i>, the exception handling mechanism used by LLVM is very
different from the model used in the Itanium ABI, so <b>exceptions will not different from the model used in the Itanium ABI, so <b>exceptions will not
interact correctly</b> . interact correctly</b>. </li>
<li><a href="http://llvm.cs.uiuc.edu/PR11">Code for executing destructors when <li><a href="http://llvm.cs.uiuc.edu/PR11">Code for executing destructors when
unwinding is not shared</a> (this is a quality of implementation problem, unwinding is not shared</a> (this is a quality of implementation problem,
which does not effect functionality).<p> which does not effect functionality).</li>
</ul>
<!-- _______________________________________________________________________ --> </div>
</ul><h4><a name="x86-be"><hr size=0>Known problems with the X86 back-end</h4><ul>
<!-- ======================================================================= -->
<div class="doc_subsection">
<a name="x86-be">Known problems with the X86 back-end</a>
</div>
<div class="doc_text">
<ul>
<li>The X86 code generator <a <li>The X86 code generator <a
href="http://llvm.cs.uiuc.edu/PR16">does not currently href="http://llvm.cs.uiuc.edu/PR16">does not currently
support the <tt>unwind</tt> instruction</a>, so code that throws a C++ exception support the <tt>unwind</tt> instruction</a>, so code that throws a C++ exception
or calls the C <tt>longjmp</tt> function will abort.<p> or calls the C <tt>longjmp</tt> function will abort.</li>
</ul>
<!-- _______________________________________________________________________ --> </div>
</ul><h4><a name="sparc-be"><hr size=0>Known problems with the Sparc back-end</h4><ul>
<!-- ======================================================================= -->
<div class="doc_subsection">
<a name="sparc-be">Known problems with the Sparc back-end</a>
</div>
<div class="doc_text">
<ul>
<li>The Sparc code generator <a <li>The Sparc code generator <a
href="http://llvm.cs.uiuc.edu/PR15">does not currently href="http://llvm.cs.uiuc.edu/PR15">does not currently
support the <tt>unwind</tt> instruction</a>, so code that throws a C++ exception support the <tt>unwind</tt> instruction</a>, so code that throws a C++ exception
or calls the C <tt>longjmp</tt> function will abort.<p> or calls the C <tt>longjmp</tt> function will abort.</li>
</ul>
<!-- _______________________________________________________________________ --> </div>
</ul><h4><a name="c-be"><hr size=0>Known problems with the C back-end</h4><ul>
<!-- ======================================================================= -->
<div class="doc_subsection">
<a name="c-be">Known problems with the C back-end</a>
</div>
<div class="doc_text">
<ul>
<li>The C back-end produces code that violates the ANSI C Type-Based Alias <li>The C back-end produces code that violates the ANSI C Type-Based Alias
Analysis rules. As such, special options may be necessary to compile the code Analysis rules. As such, special options may be necessary to compile the code
(for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
problem probably cannot be fixed.<p> problem probably cannot be fixed.</li>
<li><a href="http://llvm.cs.uiuc.edu/PR33">Initializers for global variables</a> <li><a href="http://llvm.cs.uiuc.edu/PR33">Initializers for global variables</a>
cannot include special floating point numbers like Not-A-Number or Infinity.<p> cannot include special floating point numbers like Not-A-Number or
Infinity.</li>
<li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not <li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
supported</a>. This should not affect LLVM produced by the C or C++ supported</a>. This should not affect LLVM produced by the C or C++
frontends.<p> frontends.</li>
<li>The code produces by the C back-end has only been tested with the Sun CC, <li>The code produces by the C back-end has only been tested with the Sun CC,
GCC, and Intel compilers. It is possible that it will have to be adjusted to GCC, and Intel compilers. It is possible that it will have to be adjusted to
support other C compilers.<p> support other C compilers.</li>
</ul>
</div>
<!-- *********************************************************************** --> <!-- *********************************************************************** -->
</ul><table width="100%" bgcolor="#330077" border=0 cellpadding=4 cellspacing=0> <div class="doc_section">
<tr><td align=center><font color="#EEEEFF" size=+2 face="Georgia,Palatino"><b> <a name="additionalinfo">Additional Information</a>
<a name="additionalinfo">Additional Information </div>
</b></font></td></tr></table><ul>
<!-- *********************************************************************** --> <!-- *********************************************************************** -->
A wide variety of additional information is available on the LLVM web page, <div class="doc_text">
<p>A wide variety of additional information is available on the LLVM web page,
including mailing lists publications describing algorithms and components including mailing lists publications describing algorithms and components
implemented in LLVM. The web page also contains versions of the API implemented in LLVM. The web page also contains versions of the API
documentation which is up-to-date with the CVS version of the source code. You documentation which is up-to-date with the CVS version of the source code. You
can access versions of these documents specific to this release by going into can access versions of these documents specific to this release by going into
the "<tt>llvm/doc/</tt>" directory in the LLVM tree.<p> the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
If you have any questions or comments about LLVM, please feel free to contact us <p>If you have any questions or comments about LLVM, please feel free to contact
via the mailing lists.<p> us via the mailing lists.</p>
</div>
<!-- *********************************************************************** -->
</ul>
<!-- *********************************************************************** --> <!-- *********************************************************************** -->
<hr><font size-1> <hr>
<div class="doc_footer">
<a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a>
<br>
Last modified: $Date$
</div>
Maintained By: <a href="http://llvm.cs.uiuc.edu/">The LLVM Team</a><br> </body>
<!-- Created: Wed Oct 1 17:38:54 CDT 2003 --> </html>
<!-- hhmts start -->
Last modified: Thu Nov 20 14:59:29 CST 2003
<!-- hhmts end -->
</body></html>