6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-07-28 03:25:23 +00:00
Code Issues Projects Releases Wiki Activity

Reality-check the FAQ entry for "Can I use LLVM to convert C++ to C?"

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@62961 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Dan Gohman
2009-01-25 16:04:50 +00:00
parent 237d873439
commit d5b455f6b0
1 changed files with 22 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
docs/FAQ.html
View File

@@ -564,9 +564,8 @@ code that you desire.
Note that the generated C code will be very low level (all loops are lowered Note that the generated C code will be very low level (all loops are lowered
to gotos, etc) and not very pretty (comments are stripped, original source to gotos, etc) and not very pretty (comments are stripped, original source
formatting is totally lost, variables are renamed, expressions are regrouped), formatting is totally lost, variables are renamed, expressions are regrouped),
so this may not be what you're looking for. However, this is a good way to add so this may not be what you're looking for. Also, there are several
C++ support for a processor that does not otherwise have a C++ compiler. limitations noted below.<p>
</p>
<p>Use commands like this:</p> <p>Use commands like this:</p>
@@ -603,20 +602,31 @@ C++ support for a processor that does not otherwise have a C++ compiler.
</ol> </ol>
<p>Note that, by default, the C backend does not support exception handling. If <p>Using LLVM does not eliminate the need for C++ library support.
you want/need it for a certain program, you can enable it by passing If you use the llvm-g++ front-end, the generated code will depend on
"-enable-correct-eh-support" to the llc program. The resultant code will use g++'s C++ support libraries in the same way that code generated from
setjmp/longjmp to implement exception support that is correct but relatively g++ would. If you use another C++ front-end, the generated code will
slow.</p> depend on whatever library that front-end would normally require.</p>
<p>Also note: this specific sequence of commands won't work if you use a <p>If you are working on a platform that does not provide any C++
function defined in the C++ runtime library (or any other C++ library). To libraries, you may be able to manually compile libstdc++ to LLVM
access an external C++ library, you must manually compile libstdc++ to LLVM
bitcode, statically link it into your program, then use the commands above to bitcode, statically link it into your program, then use the commands above to
convert the whole result into C code. Alternatively, you can compile the convert the whole result into C code. Alternatively, you might compile the
libraries and your application into two different chunks of C code and link libraries and your application into two different chunks of C code and link
them.</p> them.</p>
<p>Note that, by default, the C back end does not support exception handling. If
you want/need it for a certain program, you can enable it by passing
"-enable-correct-eh-support" to the llc program. The resultant code will use
setjmp/longjmp to implement exception support that is relatively slow, and
not C++-ABI-conforming on most platforms, but otherwise correct.</p>
<p>Also, there are a number of other limitations of the C backend that
cause it to produce code that does not fully conform to the C++ ABI on
most platforms. Some of the C++ programs in LLVM's test suite are known
to fail when compiled with the C back end because of ABI incompatiblities
with standard C++ libraries.</p>
</div> </div>
<!-- *********************************************************************** --> <!-- *********************************************************************** -->