From c651db110070f0dae792d893a3c2c7a26e1f6083 Mon Sep 17 00:00:00 2001 From: zah Date: Wed, 12 Feb 2014 02:56:46 -0800 Subject: [PATCH] Updated GSoC 2014 Ideas (markdown) --- GSoC-2014-Ideas.md | 1 + 1 file changed, 1 insertion(+) diff --git a/GSoC-2014-Ideas.md b/GSoC-2014-Ideas.md index 4a12961..ef4f641 100644 --- a/GSoC-2014-Ideas.md +++ b/GSoC-2014-Ideas.md @@ -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 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 read barriers and polish the support for Levanoni/Petrank style of write barriers * Implement the infrastructure for picking a user-supplied GC module