Elliott Slaughter 3f0d207b32 gc: Add stack walker for new garbage collector. ... 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.		2012-09-07 09:21:21 -07:00
..
libuv	jit: Add custom memory manager (still segfaulting)	2012-08-31 16:20:35 -07:00
clean.mk
ctags.mk
dist.mk
docs.mk	doc: Split out the FFI part of the tutorial	2012-09-05 11:20:04 -07:00
host.mk
install.mk
llvm.mk
perf.mk
platform.mk
pp.mk
rt.mk	gc: Add stack walker for new garbage collector.	2012-09-07 09:21:21 -07:00
rustllvm.mk	jit: Clean rustllvm code, let rustc expose __morestack instead of linking in libmorestack and return _rust_main and call it from rustc	2012-08-31 16:20:36 -07:00
snap.mk
stage0.mk
target.mk
tests.mk	Make check-notidy not run tidy, as implied. Close #3105.	2012-08-29 14:49:13 -07:00
tools.mk