Changes between Version 33 and Version 34 of GCTasklist

Show
Ignore:
Timestamp:
08/24/10 09:47:38 (4 years ago)
Author:
bacek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GCTasklist

    v33 v34  
    3333 - Fix system-dependent code in src/gc/system.c (See #273) 
    3434 
    35  - Implement write barriers. They're needed to maintain the remembered set for generational GC and to update the mark stack for incremental GC. There is a proposal in PDD09 but using macros doesn't work well with pluggable GC cores and using function calls is expensive. Two approaches for efficient write barriers are card marking and sequential store buffers. Card marking is preferred for procedural languages that might make a lot of assignments. 
     35 - Implement write barriers. They're needed to maintain the remembered set for generational GC and to update the mark stack for incremental GC. There is a proposal in PDD09 but using macros doesn't work well with pluggable GC cores and using function calls is expensive. Two approaches for efficient write barriers are card marking and sequential store buffers. Card marking is preferred for procedural languages that might make a lot of assignments. (bacek: We don't need write barriers if we use technique from http://research.microsoft.com/en-us/um/people/simonpj/papers/non-stop/index.htm) 
    3636 
    3737== Problems to Solve ==