On Sat, Oct 17, 2009 at 5:52 PM, Kyle Sluder <kyle.slu...@gmail.com> wrote:
> On Sat, Oct 17, 2009 at 5:35 PM, Michael Ash <michael....@gmail.com> > wrote: > > This just leaves the writes. I assume that the GC write barrier > > includes a memory barrier, unless someone wants to tell me otherwise. > > If so, then there's no problem at all. > > Strictly speaking, this isn't really an atomicity issue, is it? What > C assignment are you thinking of that would wind up being nonatomic? > The issue concerns the order of in which changes to memory are observable by other processors. It's not actually _that_ complicated, but there's frustratingly little clear writing about this online. My favorite short article is this one: Memory Ordering in Modern Microprocessors part 1: http://www.linuxjournal.com/article/8211 part 2: http://www.linuxjournal.com/article/8212 Though this still is missing just a liiittle bit of info that I think makes things much clearer. Oh well. -Ken > --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/kenferry%40gmail.com > > This email sent to kenfe...@gmail.com > _______________________________________________ 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
