Periodic plug of David Bacon’s “A Unified Theory of Garbage Collection”, an excellent paper that changed my view on GC: https://courses.cs.washington.edu/courses/cse590p/05au/p50-bacon.pdf …
-
-
The write barrier is just a bit of code executed for every write; you can do a variety of things with it. Similarly you could implement the reference count with other things than a write barrier, for example some systems use page protection (although in a sense that's a barrier).
-
Oh, that was just sloppy language on my part. By “the write barrier” I just meant “the portion of the generational GC algorithm that is usually implemented with a write barrier”.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.