aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTanya Lattner <tonic@nondot.org>2010-03-12 00:16:00 +0000
committerTanya Lattner <tonic@nondot.org>2010-03-12 00:16:00 +0000
commit50f480e2f94656b17ed352024d0f813d68ce6991 (patch)
tree9dde612eede8de385d12105bb1b3c61157f587c8
parente65220d4eff446642e04e836c522d3fb3db38275 (diff)
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
-rw-r--r--docs/SourceLevelDebugging.html12
1 files 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 @@ height="369">
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>
<!-- ======================================================================= -->