diff options
| author | Chris Lattner <sabre@nondot.org> | 2009-05-13 18:02:09 +0000 |
|---|---|---|
| committer | Chris Lattner <sabre@nondot.org> | 2009-05-13 18:02:09 +0000 |
| commit | 784ae669ab3db1052b4d84bf155cccf9f9054475 (patch) | |
| tree | 20092d1f67c63c7c4f89c238c3ad9fa6708d5cf8 /llvm/docs/GarbageCollection.html | |
| parent | ce06bb8a5360f848ed0901ed1b64d4f1ee9c804f (diff) | |
| download | bcm5719-llvm-784ae669ab3db1052b4d84bf155cccf9f9054475.tar.gz bcm5719-llvm-784ae669ab3db1052b4d84bf155cccf9f9054475.zip | |
garbage allocation is not a good idea :)
llvm-svn: 71680
Diffstat (limited to 'llvm/docs/GarbageCollection.html')
| -rw-r--r-- | llvm/docs/GarbageCollection.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/docs/GarbageCollection.html b/llvm/docs/GarbageCollection.html index ccf9162600d..b155bb93746 100644 --- a/llvm/docs/GarbageCollection.html +++ b/llvm/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 |
