• 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: NSInteger vs int vs int32_t
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSInteger vs int vs int32_t


  • Subject: Re: NSInteger vs int vs int32_t
  • From: Steve Sisak <email@hidden>
  • Date: Mon, 09 Jul 2012 15:26:32 -0400

At 10:05 AM -0600 7/5/12, Scott Ribe wrote:
And theoretically, moving from 32-bit to 64-bit executable could slow you down because of fewer pointers fitting in cache--however the few people I've ever heard mention that were, in my opinion, seriously overblowing it. In my experience with data & algorithm heavy code, just switching from 32- to 64-bit produces about a 10% performance boost, because of the advantages of x86-64 (more registers and so on).

Now you may be getting to the crux of the matter:

For a processor family with reasonably clean 32- and 64-bit models (i.e. PowerPC) going to 64-bit is a speed hit in many circumstances due to the increase in size of everything.

However, i386 has so much baggage and so few registers that the performance gain from x86-64's much less sucky architecture/runtime more than makes up for the loss due to memory bloat.

;-)

-Steve

_______________________________________________

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

References: 
 >NSInteger vs int vs int32_t (From: Andreas Grosam <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: Jens Alfke <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: Chris Hanson <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: Charles Srstka <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: Jens Alfke <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: Kyle Sluder <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: Jens Alfke <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: Kyle Sluder <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: David Duncan <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: Scott Ribe <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: Nathan Day <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: Scott Ribe <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: Nathan Day <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: Jens Alfke <email@hidden>)
 >Re: NSInteger vs int vs int32_t (From: Scott Ribe <email@hidden>)

  • Prev by Date: Re: Bottom-edge constraint not enforced in IB but is in runtime?
  • Next by Date: Re: "Capturing 'self' strongly in this block is likely to lead to a retain cycle"
  • Previous by thread: Re: NSInteger vs int vs int32_t
  • Next by thread: Re: NSInteger vs int vs int32_t
  • Index(es):
    • Date
    • Thread