Run configure with an alternative PATH that is correct. In a Borne compatible shell, the syntax would be:
-+% PATH=[the path without the bad program] ./configure ...-
This is still somewhat inconvenient, but it allows configure to do its work without having to adjust your PATH @@ -278,9 +278,9 @@ old version. What do I do?
can just run the following command in the top level directory of your object tree: -% ./config.status <relative path to Makefile>-
+% ./config.status <relative path to Makefile> +
If the Makefile is new, you will have to modify the configure script to copy it over.
@@ -315,18 +315,16 @@ clean and then make in the directory that fails to build.For example, if you built LLVM with the command:
-% gmake ENABLE_PROFILING=1-
+% gmake ENABLE_PROFILING=1 +
...then you must run the tests with the following commands:
-+% cd llvm/test % gmake ENABLE_PROFILING=1-
If the error is of the form:
-+gmake[2]: *** No rule to make target `/path/to/somefile', needed by `/path/to/another/file.d'.-
Stop.
This may occur anytime files are moved within the Subversion repository or removed entirely. In this case, the best solution is to erase all .d files, which list dependencies for source files, and rebuild:
-+% cd $LLVM_OBJ_DIR % rm -f `find . -name \*\.d` % gmake-
In other cases, it may be necessary to run make clean before rebuilding.
@@ -540,13 +534,11 @@ find libcrtend.a. The only way this can happen is if you haven't installed the runtime library. To correct this, do: -+% cd llvm/runtime % make clean ; make install-bytecode
@@ -574,30 +566,25 @@ code that you desire. 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 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 -C++ support for a processor that does not otherwise have a C++ compiler. -
+so this may not be what you're looking for. Also, there are several +limitations noted below.
Use commands like this:
Compile your program as normal with llvm-g++:
-+% llvm-g++ x.cpp -o program-
or:
-+% llvm-g++ a.cpp -c % llvm-g++ b.cpp -c % llvm-g++ a.o b.o -o program-
With llvm-gcc3, this will generate program and program.bc. The .bc file is the LLVM version of the program all linked together.
Convert the LLVM code to C code, using the LLC tool with the C backend:
-+% llc -march=c program.bc -o program.c --
Finally, compile the C file:
-+% cc x.c --
Note that, by default, the C backend 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 correct but relatively -slow.
+Using LLVM does not eliminate the need for C++ library support. +If you use the llvm-g++ front-end, the generated code will depend on +g++'s C++ support libraries in the same way that code generated from +g++ would. If you use another C++ front-end, the generated code will +depend on whatever library that front-end would normally require.
-Also note: this specific sequence of commands won't work if you use a -function defined in the C++ runtime library (or any other C++ library). To -access an external C++ library, you must manually compile libstdc++ to LLVM +
If you are working on a platform that does not provide any C++ +libraries, you may be able to manually compile libstdc++ to LLVM 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 them.
+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.
+ +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.
+ +No. C and C++ are inherently platform-dependent languages. The most +obvious example of this is the preprocessor. A very common way that C code +is made portable is by using the preprocessor to include platform-specific +code. In practice, information about other platforms is lost after +preprocessing, so the result is inherently dependent on the platform that +the preprocessing was targetting.
+ +Another example is sizeof. It's common for sizeof(long) +to vary between platforms. In most C front-ends, sizeof is expanded +to a constant immediately, thus hardwaring a platform-specific detail.
+ +Also, since many platforms define their ABIs in terms of C, and since +LLVM is lower-level than C, front-ends currently must emit platform-specific +IR in order to have the result conform to the platform ABI.
+
+
int X() { int i; return i; }
-Is compiled to "ret i32 undef" because "i" never has a value specified for it.