Clarify documentation. A module pass MP can require a function paqss FP only if FP...

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

diff --git a/docs/WritingAnLLVMPass.html b/docs/WritingAnLLVMPass.html
index 047ac6ef2d52a882eba20f0d3985c05c3f46d519..486de6f631c7c6bcd6c929983ceea9059a0e92c6 100644 (file)
--- a/docs/WritingAnLLVMPass.html
+++ b/docs/WritingAnLLVMPass.html
@@ -492,7 +492,8 @@ refering to function bodies in no predictable order, or adding and removing
 functions.  Because nothing is known about the behavior of <tt>ModulePass</tt>
 subclasses, no optimization can be done for their execution. A module pass
 can use function level passes (e.g. dominators) using getAnalysis interface
-<tt> getAnalysis&lt;DominatorTree&gt;(Function)</tt>. </p> 
+<tt> getAnalysis&lt;DominatorTree&gt;(Function)</tt>, if the function pass
+does not require any module passes. </p> 
 
 <p>To write a correct <tt>ModulePass</tt> subclass, derive from
 <tt>ModulePass</tt> and overload the <tt>runOnModule</tt> method with the