rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2012-09-07	gc: Documentation.	Elliott Slaughter	-0/+52

2012-09-07	gc: Fix for GC missing stack frames across segment boundaries.	Elliott Slaughter	-35/+100

2012-09-07	gc: Don't expect sentinel when core is compiled without GC.	Elliott Slaughter	-6/+21

2012-09-07	gc: Avoid walking stack above caller frame.	Elliott Slaughter	-3/+30
	Mark the base GC stack frame with a sentinel value so we know when to start collecting.
2012-09-07	gc: Fix for deallocating resources on the shared heap while cleaning stack.	Elliott Slaughter	-1/+2

2012-09-07	gc: Avoid freeing null pointers.	Elliott Slaughter	-0/+6

2012-09-07	gc: Avoid double free when pointer appears on stack multiple times.	Elliott Slaughter	-14/+23

2012-09-07	gc: Add stack walker for new garbage collector.	Elliott Slaughter	-0/+155
	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.