diff options
author | Chris Lattner <sabre@nondot.org> | 2010-09-29 05:34:42 +0000 |
---|---|---|
committer | Chris Lattner <sabre@nondot.org> | 2010-09-29 05:34:42 +0000 |
commit | 3016ee9e69e9f9c2890719c7855d6f9f00135f28 (patch) | |
tree | 73c3e8ad83ffbf902f5d9083184c5bdfb4a83d61 | |
parent | e07043c4b4f76f3122c2e3d5502367aacbe6f496 (diff) | |
download | external_llvm-3016ee9e69e9f9c2890719c7855d6f9f00135f28.zip external_llvm-3016ee9e69e9f9c2890719c7855d6f9f00135f28.tar.gz external_llvm-3016ee9e69e9f9c2890719c7855d6f9f00135f28.tar.bz2 |
merge all the llvm-gcc pieces together. Recommend that people try dragonegg if they care about fortran performance.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@115031 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r-- | docs/ReleaseNotes.html | 46 |
1 files changed, 18 insertions, 28 deletions
diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index b6b2ef2..8bb4739 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -732,6 +732,9 @@ appropriate nops inserted to ensure restartability.</li> <div class="doc_text"> +<p>The C backend has numerous problems and is not being actively maintained. +Depending on it for anything serious is not advised.</p> + <ul> <li><a href="http://llvm.org/PR802">The C backend has only basic support for inline assembly code</a>.</li> @@ -747,40 +750,27 @@ appropriate nops inserted to ensure restartability.</li> <!-- ======================================================================= --> <div class="doc_subsection"> - <a name="c-fe">Known problems with the llvm-gcc C and C++ front-end</a> + <a name="llvm-gcc">Known problems with the llvm-gcc front-end</a> </div> <div class="doc_text"> -<p>The only major language feature of GCC not supported by llvm-gcc is - the <tt>__builtin_apply</tt> family of builtins. However, some extensions - are only supported on some targets. For example, trampolines are only - supported on some targets (these are used when you take the address of a - nested function).</p> - -</div> - -<!-- ======================================================================= --> -<div class="doc_subsection"> - <a name="fortran-fe">Known problems with the llvm-gcc Fortran front-end</a> -</div> - -<div class="doc_text"> -<ul> -<li>Fortran support generally works, but there are still several unresolved bugs - in <a href="http://llvm.org/bugs/">Bugzilla</a>. Please see the - tools/gfortran component for details.</li> -</ul> -</div> +<p>llvm-gcc is generally very stable for the C family of languages. The only + major language feature of GCC not supported by llvm-gcc is the + <tt>__builtin_apply</tt> family of builtins. However, some extensions + are only supported on some targets. For example, trampolines are only + supported on some targets (these are used when you take the address of a + nested function).</p> -<!-- ======================================================================= --> -<div class="doc_subsection"> - <a name="ada-fe">Known problems with the llvm-gcc Ada front-end</a> -</div> +<p>Fortran support generally works, but there are still several unresolved bugs + in <a href="http://llvm.org/bugs/">Bugzilla</a>. Please see the + tools/gfortran component for details. Note that llvm-gcc is missing major + Fortran performance work in the frontend and library that went into GCC after + 4.2. If you are interested in Fortran, we recommend that you consider using + <a href="#dragonegg">dragonegg</a> instead.</p> -<div class="doc_text"> -The llvm-gcc 4.2 Ada compiler works fairly well; however, this is not a mature -technology, and problems should be expected. +<p>The llvm-gcc 4.2 Ada compiler has basic functionality. However, this is not a +mature technology, and problems should be expected. For example:</p> <ul> <li>The Ada front-end currently only builds on X86-32. This is mainly due to lack of trampoline support (pointers to nested functions) on other platforms. |