From: Devang Patel <dpatel@apple.com>
Date: Fri, 21 Nov 2008 19:35:57 +0000 (+0000)
Subject: Document TEST=dbgopt
X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=a5c05aad57556eee4cea43f33234312320a0a219;p=oota-llvm.git

Document TEST=dbgopt


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@59839 91177308-0d34-0410-b5e6-96231b3b80d8
---

diff --git a/docs/SourceLevelDebugging.html b/docs/SourceLevelDebugging.html
index 172ede02e6a..4984521f599 100644
--- 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>
 
 <!-- *********************************************************************** -->