Updated GSoC 2014 Ideas (markdown)
This commit is contained in:
parent
3ac3ab0739
commit
c651db1100
|
@ -39,6 +39,7 @@ In contrast, in Nimrod, the garbage collection algorithm is chosen at compile-ti
|
||||||
The Nimrod code generator and type system can provide various GC roots marking strategies, various kinds of write/read barriers and all necessary static type information (e.g. static cycle analysis) and a GC implementation will consist only of a single Nimrod module (supplied as a command-line parameter) that
|
The Nimrod code generator and type system can provide various GC roots marking strategies, various kinds of write/read barriers and all necessary static type information (e.g. static cycle analysis) and a GC implementation will consist only of a single Nimrod module (supplied as a command-line parameter) that
|
||||||
provides configuration for the code generator and implements the logic of the garbage collection algorithm. This module will be compiled as C code with the rest of the program and it could be easily debugged using standard C/C++ debugging and profiling tools.
|
provides configuration for the code generator and implements the logic of the garbage collection algorithm. This module will be compiled as C code with the rest of the program and it could be easily debugged using standard C/C++ debugging and profiling tools.
|
||||||
|
|
||||||
|
**Tasks:**
|
||||||
* Add support for precise stack marking
|
* Add support for precise stack marking
|
||||||
* Add support for read barriers and polish the support for Levanoni/Petrank style of write barriers
|
* Add support for read barriers and polish the support for Levanoni/Petrank style of write barriers
|
||||||
* Implement the infrastructure for picking a user-supplied GC module
|
* Implement the infrastructure for picking a user-supplied GC module
|
||||||
|
|
Loading…
Reference in New Issue