[vmkit-commits] [vmkit] r85247 - /vmkit/trunk/lib/JnJVM/VMCore/VirtualTables.cpp

[Nicolas Geoffray]

Author: geoffray
Date: Tue Oct 27 11:38:41 2009
New Revision: 85247

URL: http://llvm.org/viewvc/llvm-project?rev=85247&view=rev
Log:
Fix comment: there is only one GC internal class in jnjvm: VMClassLoader.


Modified:
    vmkit/trunk/lib/JnJVM/VMCore/VirtualTables.cpp

Modified: vmkit/trunk/lib/JnJVM/VMCore/VirtualTables.cpp
URL: http://llvm.org/viewvc/llvm-project/vmkit/trunk/lib/JnJVM/VMCore/VirtualTables.cpp?rev=85247&r1=85246&r2=85247&view=diff

==============================================================================
--- vmkit/trunk/lib/JnJVM/VMCore/VirtualTables.cpp (original)
+++ vmkit/trunk/lib/JnJVM/VMCore/VirtualTables.cpp Tue Oct 27 11:38:41 2009
@@ -40,13 +40,8 @@
 // Having many GC classes gives more work to the GC for the scanning phase
 // and for the relocation phase (for copying collectors.
 //
-// In JnJVM, we identified two cases where we really need to declare GC
-// classes: the fat lock object and the class loader.
-//
-// For the fat lock there are many design decisions that we could make to
-// make it a non-GC class. We leave this as a TODO.
-//
-// For the class loader, we decided that this was the best solution because
+// In JnJVM, there is only one internal gc object, the class loader.
+// We decided that this was the best solution because
 // otherwise it would involve hacks on the java.lang.Classloader class.
 // Therefore, we create a new GC class with a finalize method that will
 // delete the internal class loader when the Java object class loader is