From 6b87fb8d66f4ddbd9976d2e8d6e069a472b70898 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Wed, 9 Jun 2004 03:59:05 +0000 Subject: [PATCH] Minor tweaks llvm-svn: 14081 --- docs/GarbageCollection.html | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/GarbageCollection.html b/docs/GarbageCollection.html index 35bb60a598f..3263fc624b0 100644 --- a/docs/GarbageCollection.html +++ b/docs/GarbageCollection.html @@ -220,7 +220,7 @@ CodeBlock:

The llvm_gc_allocate 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.

@@ -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.

+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.

To support garbage collectors that use read or write barriers, LLVM provides the llvm.gcread and llvm.gcwrite intrinsics. The first