• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: GC and atomic getters/setters
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GC and atomic getters/setters


  • Subject: Re: GC and atomic getters/setters
  • From: Kyle Sluder <email@hidden>
  • Date: Sat, 17 Oct 2009 17:52:02 -0700

On Sat, Oct 17, 2009 at 5:35 PM, Michael Ash <email@hidden> 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?

--Kyle Sluder
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

  • Follow-Ups:
    • Re: GC and atomic getters/setters
      • From: Ken Ferry <email@hidden>
References: 
 >GC and atomic getters/setters (From: BJ Homer <email@hidden>)
 >Re: GC and atomic getters/setters (From: Bill Bumgarner <email@hidden>)
 >Re: GC and atomic getters/setters (From: Michael Ash <email@hidden>)
 >Re: GC and atomic getters/setters (From: Michael Ash <email@hidden>)

  • Prev by Date: Re: GC and atomic getters/setters
  • Next by Date: Manipluate Cocoa Touch keyboard mode
  • Previous by thread: Re: GC and atomic getters/setters
  • Next by thread: Re: GC and atomic getters/setters
  • Index(es):
    • Date
    • Thread