3f0d207b32
Safe points are exported in a per-module list via the crate map. A C runtime call walks the crate map at startup and aggregates the list of safe points for the program. Currently the GC doesn't actually deallocate memory on malloc and free. Adding the GC at this stage is primarily of testing value. The GC does attempt to clean up exchange heap and stack-allocated resource on failure. A result of this patch is that the user now needs to be careful about what code they write in destructors, because the GC and/or failure cleanup may need to call destructors. Specifically, calls to malloc are considered unsafe and may result in infinite loops or segfaults. |
||
|---|---|---|
| .. | ||
| libuv | ||
| clean.mk | ||
| ctags.mk | ||
| dist.mk | ||
| docs.mk | ||
| host.mk | ||
| install.mk | ||
| llvm.mk | ||
| perf.mk | ||
| platform.mk | ||
| pp.mk | ||
| rt.mk | ||
| rustllvm.mk | ||
| snap.mk | ||
| stage0.mk | ||
| target.mk | ||
| tests.mk | ||
| tools.mk | ||