A step towards geting linux ppc to work (see PR 3099)

[oota-llvm.git] / docs / SourceLevelDebugging.html

diff --git a/docs/SourceLevelDebugging.html b/docs/SourceLevelDebugging.html
index 172ede02e6afd19bbed7a9a607243a23ad398045..4984521f5993f7fea2ab8359b28c9c8aa92ef5b0 100644 (file)
--- a/docs/SourceLevelDebugging.html
+++ b/docs/SourceLevelDebugging.html
@@ -208,6 +208,24 @@ elimination and inlining), but you might lose the ability to modify the program
 and call functions where were optimized out of the program, or inlined away
 completely.</p>
 
+<p> <a href=http://llvm.org/docs/TestingGuide.html#quicktestsuite> 
+LLVM test suite </a> provides a framework to test optimizer's handling of
+debugging information. It can be run like this:</p>
+
+<div class="doc_code">
+<pre>
+% cd llvm/projects/test-suite/MultiSource/Benchmarks  # or some other level
+% make TEST=dbgopt
+</pre>
+</div>
+
+<p>
+This will test impact of debugging information on optimization passes. If
+debugging information influences optimization passes then it will be reported
+as a failure. See <a href=//llvm.org/docs/TestingGuide.html> TestingGuide</a>
+for more information on LLVM test infratsture and how to run various tests.
+</p>
+
 </div>
 
 <!-- *********************************************************************** -->