This is the mail archive of the guile@cygnus.com mailing list for the guile project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Miroslav Silovic <silovic@zesoi.fer.hr> wrote: > What exactly mostly-copying refers to, here? If it means that it will > avoid copying data referenced by C code, it may hold water. It means that it doesn't copy virtual memory pages which are referenced by (potential) pointers which it can't safely update - like conservatively scanned C stack - whereas heap objects which are _only_ referenced from other heap objects (with well-known structures) are copied. For details, I suggest you track down the original reports, and/or just ask on the newsgroup comp.lang.modula3, where they should be able to answer most questions about experiences with this kind of collector, including its interaction with threads (which Modula-3 supports). The current version of Modula-3 is based on a modified gcc backend (and a specific native code generator for some platforms), but earlier versions did also generate C source code, using the same gc algorithm, and all versions do easily interact with C routines (user-supplied and system libraries). I don't know how easy or hard it is to adapt the collector to various platforms. -- Marc Wachowitz <mw@ipx2.rz.uni-mannheim.de>