If you're working with LLVM and run into a bug, we definitely want to know about it. This document describes what you can do to increase the odds of @@ -76,12 +76,12 @@ information:
More often than not, bugs in the compiler cause it to crash—often due to an assertion failure of some sort. The most important @@ -109,14 +109,12 @@ with the following extra command line options:
-If the problem is in the front-end, you should re-run the same llvm-gcc command that resulted in the crash, but add the @@ -137,11 +135,11 @@ has instructions on the best way to use delta.
If you find that a bug crashes in the optimizer, compile your test-case to a .bc file by passing "-emit-llvm -O0 -c -o foo.bc". @@ -153,7 +151,7 @@ Then run:
This command should do two things: it should print out a list of passes, and -then it should crash in the same was as llvm-gcc. If it doesn't crash, please +then it should crash in the same way as llvm-gcc. If it doesn't crash, please follow the instructions for a front-end bug.
If this does crash, then you should be able to debug this with the following @@ -171,11 +169,11 @@ that bugpoint emits. If something goes wrong with bugpoint, please submit the
If you find a bug that crashes llvm-gcc in the code generator, compile your source file to a .bc file by passing "-emit-llvm -c -o foo.bc" @@ -207,13 +205,15 @@ that bugpoint emits. If something goes wrong with bugpoint, please submit the
If llvm-gcc successfully produces an executable, but that executable doesn't run right, this is either a bug in the code or a bug in the @@ -241,12 +241,12 @@ error.
Similarly to debugging incorrect compilation by mis-behaving passes, you can debug incorrect code generation by either LLC or the JIT, using @@ -338,7 +338,7 @@ the following:
src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"> Chris Lattner