From 50f480e2f94656b17ed352024d0f813d68ce6991 Mon Sep 17 00:00:00 2001
From: Tanya Lattner <tonic@nondot.org>
Date: Fri, 12 Mar 2010 00:16:00 +0000
Subject: [PATCH] Doc patch for the branch only.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/branches/release_27@98314 91177308-0d34-0410-b5e6-96231b3b80d8
---
 docs/SourceLevelDebugging.html | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

diff --git a/docs/SourceLevelDebugging.html b/docs/SourceLevelDebugging.html
index b028ee6d34..462b859d49 100644
--- a/docs/SourceLevelDebugging.html
+++ b/docs/SourceLevelDebugging.html
@@ -351,14 +351,10 @@
    for source line correspondence.</p>
 
 <p>Each input file is encoded as a separate compile unit in LLVM debugging
-   information output. However, many target specific tool chains prefer to
-   encode only one compile unit in an object file. In this situation, the LLVM
-   code generator will include debugging information entities in the compile
-   unit that is marked as main compile unit. The code generator accepts maximum
-   one main compile unit per module. If a module does not contain any main
-   compile unit then the code generator will emit multiple compile units in the
-   output object file.</p>
-
+   information output. However the code generator emits only one compile unit,
+   marked as main compile unit, in an object file's debugging information section.
+   Most of the, if not all, target specific tool chains expect only one compile 
+   unit entry per object file. </p>
 </div>
 
 <!-- ======================================================================= -->