diff options
| author | Misha Brukman <brukman+llvm@gmail.com> | 2004-05-12 00:57:24 +0000 |
|---|---|---|
| committer | Misha Brukman <brukman+llvm@gmail.com> | 2004-05-12 00:57:24 +0000 |
| commit | b797a4f9680dd7e1c0a24385e62da636944e181c (patch) | |
| tree | 7d036b855cc5e3c36ee3bf2dd59353f635993223 | |
| parent | a060b10ee57998a8a4cddc1b6f06ef8f2a9cafdf (diff) | |
| download | bcm5719-llvm-b797a4f9680dd7e1c0a24385e62da636944e181c.tar.gz bcm5719-llvm-b797a4f9680dd7e1c0a24385e62da636944e181c.zip | |
Add link to Valgrind.
llvm-svn: 13472
| -rw-r--r-- | llvm/docs/HowToSubmitABug.html | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/llvm/docs/HowToSubmitABug.html b/llvm/docs/HowToSubmitABug.html index 16e4c24a58b..69da4fafdbf 100644 --- a/llvm/docs/HowToSubmitABug.html +++ b/llvm/docs/HowToSubmitABug.html @@ -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> |
