diff options
| author | Chris Lattner <sabre@nondot.org> | 2004-06-09 03:59:05 +0000 |
|---|---|---|
| committer | Chris Lattner <sabre@nondot.org> | 2004-06-09 03:59:05 +0000 |
| commit | 0c09852909c7d29cd101a02f863e7c232c962123 (patch) | |
| tree | 7ebc49f783f27238a4d68f407dcf889367587714 /llvm/docs/GarbageCollection.html | |
| parent | 4d598edc59e8603820c4c7dbc9d338ea5ebe3ba4 (diff) | |
| download | bcm5719-llvm-0c09852909c7d29cd101a02f863e7c232c962123.tar.gz bcm5719-llvm-0c09852909c7d29cd101a02f863e7c232c962123.zip | |
Minor tweaks
llvm-svn: 14081
Diffstat (limited to 'llvm/docs/GarbageCollection.html')
| -rw-r--r-- | llvm/docs/GarbageCollection.html | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/llvm/docs/GarbageCollection.html b/llvm/docs/GarbageCollection.html index 35bb60a598f..3263fc624b0 100644 --- a/llvm/docs/GarbageCollection.html +++ b/llvm/docs/GarbageCollection.html @@ -220,7 +220,7 @@ CodeBlock: </tt></div> <p>The <tt>llvm_gc_allocate</tt> function is a global function defined by the -garbage collector implementation to allocate memory. It should return a +garbage collector implementation to allocate memory. It returns a zeroed-out block of memory of the appropriate size.</p> </div> @@ -242,8 +242,9 @@ collectors) need to be informed when the mutator (the program that needs garbage collection) reads or writes object references into the heap. In the case of a generational collector, it needs to keep track of which "old" generation objects have references stored into them. The amount of code that typically needs to be -executed is usually quite small, so the overall performance impact of the -inserted code is tolerable.</p> +executed is usually quite small (and not on the critical path of any +computation), so the overall performance impact of the inserted code is +tolerable.</p> <p>To support garbage collectors that use read or write barriers, LLVM provides the <tt>llvm.gcread</tt> and <tt>llvm.gcwrite</tt> intrinsics. The first |
