On Sat, Oct 17, 2009 at 6:20 PM, Ken Ferry <kenfe...@gmail.com> wrote: > The issue concerns the order of in which changes to memory are observable by > other processors.
Okay, and the read example is immune because you have to read the address before you can read the thing at that address, and it's therefore impossible to wind up in a bad situation due to read reordering, simply because the reads have to be structured in a particular way. I'm struggling to picture being able to write code that is sensitive to write reordering under GC that is not either sensitive to write reordering on non-GC with equivalent locking and is also not sensitive to other concurrency problems. Of course, I attribute this more to my lack of imagination or experience at the lower levels than to the lack of a good example. --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
