News for hackers. Stuff that matters.
Re:Qualcomm backtracks from Apple A7 marketing gimmick comments by masklinn on Wednesday October 09, 2013 @04:18AM (#6519985)
In "the obvious", note that the switch to ARM64 also allows a more efficient Obj-C runtime: there are more unused bits (due to alignment and effective pointer sizes) in AArch64 than in AArch32, and more in ARM64 than x86-64.

This allows the obj-c runtime to smuggle significantly more information inline in the `isa` pointer on ARM64 than on ARM32 or x86-64 (via pointer tagging): http://www.sealiesoftware.com/blog/archive/2013/09/24/objc_e... http://www.mikeash.com/pyblog/friday-qa-2013-09-27-arm64-and...

(amongst other things, 19 bits of the pointer are now used to hold the object's reference count, for any object with less than half a million references an incref or decref is just an atomic increment or decrement of this field, instead of an indirection through a global refcount table with a bunch of locks involved)

Re:Qualcomm backtracks from Apple A7 marketing gimmick comments by sorbits on Wednesday October 09, 2013 @04:54AM (#6520117)
> In "the obvious", note that the switch to ARM64 also allows a more efficient Obj-C runtime […]

Why wouldn’t inline reference counts (as an extra 32 bit word in the object struct) be just as effective on a 32 bit architecture?

Apple’s tagged pointer tricks are just making the best of a bad situation.

Re:Qualcomm backtracks from Apple A7 marketing gimmick comments by r00fus on Wednesday October 09, 2013 @02:27PM (#6522918)
How are extra 32bit words considered "inline"? Wouldn't this completely miss using the register for count evaluation?
Re:Qualcomm backtracks from Apple A7 marketing gimmick comments by mikeash on Wednesday October 09, 2013 @11:39AM (#6521919)
Most definitely. If you were building a new environment from scratch, there's no reason you couldn't do the same basic stuff in a 32-bit world. Apple just couldn't do it without the architecture transition because it would break everything.