- Aug 17, 2008
-
-
Gordon Henriksen authored
In particular, Collector was confusing to implementors. Several thought that this compile-time class was the place to implement their runtime GC heap. Of course, it doesn't even exist at runtime. Specifically, the renames are: Collector -> GCStrategy CollectorMetadata -> GCFunctionInfo CollectorModuleMetadata -> GCModuleInfo CollectorRegistry -> GCRegistry Function::getCollector -> getGC (setGC, hasGC, clearGC) Several accessors and nested types have also been renamed to be consistent. These changes should be obvious. llvm-svn: 54899
-
Gordon Henriksen authored
llvm-svn: 54895
-
Gordon Henriksen authored
Factor GC metadata table assembly generation out of Collector in preparation for splitting AsmPrinter into its own library. llvm-svn: 54881
-
- Jul 02, 2008
-
-
Chris Lattner authored
Solanki! llvm-svn: 53008
-
- May 13, 2008
-
-
Dan Gohman authored
several things that were neither in an anonymous namespace nor static but not intended to be global. llvm-svn: 51017
-
- Dec 29, 2007
-
-
Chris Lattner authored
llvm-svn: 45418
-
- Dec 14, 2007
-
-
Dan Gohman authored
llvm-svn: 45034
-
- Dec 11, 2007
-
-
Gordon Henriksen authored
per-function collector model. Collector is now the factory for CollectorMetadata, so the latter may be subclassed. llvm-svn: 44827
-
- Sep 28, 2007
-
-
Gordon Henriksen authored
It includes: - location and of each safe point in machine code (identified by a label) - location of each root within the stack frame (identified by an offset), including the metadata tag provided to llvm.gcroot in the user program - size of the stack frame (for collectors which want to cheat on stack crawling :) - and eventually will include liveness It is to be populated by back-ends during code-generation. CollectorModuleMetadata aggregates this information across the entire module. llvm-svn: 42418
-