On 10/07/2013 22:04, Graydon Hoare wrote:
On 13-07-10 11:32 AM, Patrick Walton wrote:
I've been thinking about what will be needed to support incremental and
generational GC in Rust. To be clear, I don't think we should block on
it now, but we should not make it unduly difficult for us to implement
in the future.
I figured we'd be doing the incremental-generational variant of
mostly-copying (once we get mostly-copying working _at all_ -- we're a
long ways from there). Trap on @-writes to heap, mask to page bits,
compare generation numbers. With MMU or without, depending on environment.
I assume you've read this:
http://www.hpl.hp.com/techreports/Compaq-DEC/WRL-91-8.pdf
This is also relevant, I think (and more recent):
Antony L. Hosking. 2006. Portable, mostly-concurrent, mostly-copying
garbage collection for multi-processors. In /Proceedings of the 5th
international symposium on Memory management/ (ISMM '06). ACM, New York,
NY, USA, 40-51. DOI=10.1145/1133956.1133963
http://doi.acm.org/10.1145/1133956.1133963
http://dl.acm.org/citation.cfm?id=1133963
Cheers,
-Felix (who has not yet caught up with the rest of the thread)
--
irc: pnkfelix on irc.mozilla.org
email: {fklock, pnkfelix}@mozilla.com
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
