summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2009-05-13 18:02:09 +0000
committerChris Lattner <sabre@nondot.org>2009-05-13 18:02:09 +0000
commit7f3b36da51d857b6596541626576ed43ea2d7f64 (patch)
tree9171af158ecae37e60dd49edab308d754260d8bc /docs
parent752c1df73949438ef6fa86a86363ee7091aa2532 (diff)
downloadllvm-7f3b36da51d857b6596541626576ed43ea2d7f64.tar.gz
llvm-7f3b36da51d857b6596541626576ed43ea2d7f64.tar.bz2
llvm-7f3b36da51d857b6596541626576ed43ea2d7f64.tar.xz
garbage allocation is not a good idea :)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@71680 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
-rw-r--r--docs/GarbageCollection.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/GarbageCollection.html b/docs/GarbageCollection.html
index ccf9162600..b155bb9374 100644
--- a/docs/GarbageCollection.html
+++ b/docs/GarbageCollection.html
@@ -118,7 +118,7 @@ conservative garbage collectors (though these seem rare in practice).</p>
they can suffer from degraded scalar optimization of the program. In particular,
because the runtime must be able to identify and update all pointers active in
the program, some optimizations are less effective. In practice, however, the
-locality and performance benefits of using aggressive garbage allocation
+locality and performance benefits of using aggressive garbage collection
techniques dominates any low-level losses.</p>
<p>This document describes the mechanisms and interfaces provided by LLVM to