Re: Why bother porting Guile to BDW-GC?

[ludo@gnu.org (Ludovic Courtès)]

Hello!

One more thought...

ludo@gnu.org (Ludovic Courtès) writes:

>   3. Benefit from an all-knowing GC.  While Guile's GC knows only about
>      the stack(s), registers and "cell heap", BDW-GC knows about all of
>      a process' storage: stack(s), registers, the whole heap,
>      thread-local storage, etc.
>
>      Concrete benefits:

       3g. No need to tell Guile about much memory is allocated behind
           its back, e.g., with malloc(3).  This makes
           `scm_gc_register_collectable_memory ()' and friends (info
           "(guile) Memory Blocks") no-ops.

           It also means that BDW-GC has accurate information about heap
           usage, even in the presence of third party libraries that
           can't be instrumented to use `scm_gc_malloc ()' et al.,
           allowing it to make informed decisions.

Thanks,
Ludo'.