[llvm-commits] CVS: llvm/docs/GarbageCollection.html

[Chris Lattner]

Changes in directory llvm/docs:

GarbageCollection.html updated: 1.4 -> 1.5

---
Log message:

Minor tweaks


---
Diffs of the changes:  (+5 -4)

Index: llvm/docs/GarbageCollection.html
diff -u llvm/docs/GarbageCollection.html:1.4 llvm/docs/GarbageCollection.html:1.5
--- llvm/docs/GarbageCollection.html:1.4	Thu May 27 00:52:10 2004
+++ llvm/docs/GarbageCollection.html	Tue Jun  8 22:59:05 2004
@@ -220,7 +220,7 @@
 </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 @@
 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
@@ -519,7 +520,7 @@
 
   <a href="mailto:sabre at nondot.org">Chris Lattner</a><br>
   <a href="http://llvm.cs.uiuc.edu">LLVM Compiler Infrastructure</a><br>
-  Last modified: $Date: 2004/05/27 05:52:10 $
+  Last modified: $Date: 2004/06/09 03:59:05 $
 </address>
 
 </body>