[rvm-research] Why both insertion and deletion barrier in sync1/2 phases of on-the-fly Garbage collector are needed?
Lokesh Gidra <[email protected]> Wed, 6 Jul 2016 20:03:15 +0000 (UTC)
| Newsgroups | gmane.comp.java.jikes.rvm.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, Given that the write barrier and object allocation are supposed to be atomic wrt. handshakes, why does an SATB based on-the-fly implementation (like the famous DLG from POPl'94 paper) need to use both, insertion and deletion barriers during sync1 and sync2 phases? Won't just using deletion barrier suffice? Kind Regards,Lokesh ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Jikesrvm-researchers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers