Linked by Thom Holwerda on Mon 31st Mar 2014 21:35 UTC
Apple

AnandTech on Apple's A7 processor:

I suspect Apple has more tricks up its sleeve than that however. Swift and Cyclone were two tocks in a row by Intel's definition, a third in 3 years would be unusual but not impossible (Intel sort of committed to doing the same with Saltwell/Silvermont/Airmont in 2012 - 2014).

Looking at Cyclone makes one thing very clear: the rest of the players in the ultra mobile CPU space didn't aim high enough. I wonder what happens next round.

This is one area where Apple really took everyone by surprise recently. When people talk about Apple losing its taste for disruption, they usually disregard the things they do not understand - such as hardcore processor design.

Thread beginning with comment 585683
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Sad fact of reality
by Carewolf on Tue 1st Apr 2014 07:19 UTC in reply to "Sad fact of reality"
Carewolf
Member since:
2005-09-08

Well, it 64-bit does come at a cost of more memory consumption. Unless it is packaged together with instruction set improvements like x64 and AArch64 is it will always be slower than 32-bit. So the only reason iOS has ANY benifit from 64-bit is not due to the 64-bit, but despite it.

Reply Parent Score: 6

RE[2]: Sad fact of reality
by renox on Tue 1st Apr 2014 11:48 in reply to "RE: Sad fact of reality"
renox Member since:
2005-07-06

Note that even though the transition from 32bit to 64bit address space was quite boring in x86 and ARM, it doesn't *have* to be this way: in the Mill project they use the 64-bit address space to have unified address space (but still with memory protection) which allow them to have to more efficient memory subsystem ( http://millcomputing.com/docs/memory/ ) and yes not be restricted to a tiny TLB is very important (think about the advantages for multiple processes).

I think that it would be great also if CPUs would use 64-bit pointer to allow you to have efficiently a tag field in the higher bits (which has benefits over using the lower bits as it is compatible with packed data(unaligned)) for tagging pointers (efficient GCs), tagging integers (efficient big-ints implementations)..

Reply Parent Score: 3

RE[2]: Sad fact of reality
by galvanash on Tue 1st Apr 2014 14:43 in reply to "RE: Sad fact of reality"
galvanash Member since:
2006-01-25

Well, it 64-bit does come at a cost of more memory consumption. Unless it is packaged together with instruction set improvements like x64 and AArch64 is it will always be slower than 32-bit. So the only reason iOS has ANY benifit from 64-bit is not due to the 64-bit, but despite it.


The A7 is AArch64...

Reply Parent Score: 2