[llvm-branch-commits] [llvm-branch] r98314 - /llvm/branches/release_27/docs/SourceLevelDebugging.html

[Tanya Lattner]

Author: tbrethou
Date: Thu Mar 11 18:16:00 2010
New Revision: 98314

URL: http://llvm.org/viewvc/llvm-project?rev=98314&view=rev
Log:
Doc patch for the branch only.

Modified:
    llvm/branches/release_27/docs/SourceLevelDebugging.html

Modified: llvm/branches/release_27/docs/SourceLevelDebugging.html
URL: http://llvm.org/viewvc/llvm-project/llvm/branches/release_27/docs/SourceLevelDebugging.html?rev=98314&r1=98313&r2=98314&view=diff
==============================================================================
--- llvm/branches/release_27/docs/SourceLevelDebugging.html (original)
+++ llvm/branches/release_27/docs/SourceLevelDebugging.html Thu Mar 11 18:16:00 2010
@@ -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>
 
 <!-- ======================================================================= -->