aboutsummaryrefslogtreecommitdiffstats
path: root/docs/HowToSubmitABug.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/HowToSubmitABug.html')
-rw-r--r--docs/HowToSubmitABug.html5
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/HowToSubmitABug.html b/docs/HowToSubmitABug.html
index 16e4c24..69da4fa 100644
--- a/docs/HowToSubmitABug.html
+++ b/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>