This document is now valid HTML 4.01 Strict and valid CSS.

We shall display images to that effect.

If you modify this file, check that you haven't broken anything by clicking on
those links, or I will hunt you down and force you to memorize the HTML and CSS
specs!!

llvm-svn: 10151
This commit is contained in:
Misha Brukman 2003-11-22 01:00:11 +00:00
parent bff6032a34
commit 7cb4e38e2e
1 changed files with 18 additions and 15 deletions

View File

@ -27,11 +27,9 @@
<li><a href="#c-be">Known problems with the C back-end</a>
</ul></li>
<li><a href="#additionalinfo">Additional Information</a></li>
</ul></li>
</ol>
<div section="doc_text">
<div class="doc_text">
<p><b>Written by <a href="mailto:sabre@nondot.org">Chris Lattner</a></b><p>
</div>
@ -87,7 +85,7 @@ now explore the LLVM optimizer with the C backend (note that LLVM requires GCC
<li>LLVM has been <a
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
code.</a> Note that due to a bug in GDB 5.x, to debug namespacified LLVM code,
code. Note that due to a bug in GDB 5.x, to debug namespacified LLVM code,
you will need to upgrade to GDB 6.</li>
</ol>
@ -302,13 +300,13 @@ bits.</li>
<li>The following Unix system functionality has not been tested and may not
work:
<ol>
<li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
<tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
<li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
- These functions have not been tested.
</ol></li>
<ol>
<li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
<tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
<li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
- These functions have not been tested.
</ol></li>
<li>Although many GCC extensions are supported, some are not. In particular,
the following extensions are known to <b>not be</b> supported:
@ -326,7 +324,7 @@ work:
<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>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
</ol></li>
</ol>
<p>The following GCC extensions are <b>partially</b> supported. An ignored
attribute means that the LLVM compiler ignores the presence of the attribute,
@ -416,7 +414,9 @@ work:
<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>
</ol></li>
</ul>
<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).</p>
@ -581,8 +581,11 @@ us via the mailing lists.</p>
<hr>
<div class="doc_footer">
<a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a>
<br>
<a href="http://validator.w3.org/check/referer"><img width="88" height="31"
src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"></a>
<a href="http://jigsaw.w3.org/css-validator/"><img width="88" height="31"
src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a><br>
<a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
Last modified: $Date$
</div>