forked from OSchip/llvm-project
parent
a060b10ee5
commit
b797a4f968
|
@ -231,8 +231,9 @@ before defining them, etc.) which the verifier will check for after a pass
|
|||
finishes its run.</p>
|
||||
|
||||
<p>If it looks like the LLVM compiler is miscompiling a program, the very first
|
||||
thing to check is to make sure it is not using undefined behavior. In
|
||||
particular, check to see if the program valgrinds clean, passes purify, or some
|
||||
thing to check is to make sure it is not using undefined behavior. In
|
||||
particular, check to see if the program <a
|
||||
href="http://valgrind.kde.org/">valgrind</a>s clean, passes purify, or some
|
||||
other memory checker tool. Many of the "LLVM bugs" that we have chased down
|
||||
ended up being bugs in the program being compiled, not LLVM.</p>
|
||||
|
||||
|
|
Loading…
Reference in New Issue