Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

A7 Processor to Be 31% Faster and 64-Bit, iPhone 5S to Support Motion Tracking?

acfusion29 said:
apple adding useless features (this and fingerprint reader) that people don't want, rather than a bigger screen that people DO want.
Click to expand...

Speak for yourself. Who says this fingerprint technology will be useless in the long run? Or that fad of large screens will continue?
 
teknikal90 said:
This is crap.
Apple is banking 50% of its revenue, on a 30% speed bump??
At a time when the market is like red hot with competitors with various innovations??
Click to expand...

That's the benefit of making the OS along with designing the processor. Everything is optimized. You don't judge each piece individually. You judge the final product.
 
Jesus... People are complaining about a processor which isn't confirmed for being "only" 30% faster...

Seriously what can't you do on the iPhone 5 now? What are you hoping to do on the 5S which needs more than 30% speed improvements? Want it to replace the Hadron Colider?
 
petsounds said:
Apple squeezes more out of its processors and has a much more efficient OS than Android. So comparing CPU numbers directly has little relevance.

This is also Fox News, so I'm taking this with a metric ton of salt.
Click to expand...

No it's Clayton Morris. I've heard him on imore podcast before. He knows his tech. Not sure though what his accuracy is on Apple rumors though.

----------
CmdrLaForge said:
Mine neither. It is perfect. What would make me buy a new one?
Click to expand...

Quad core I guess.
 
viperGTS said:
Only 31% faster? I don't know how they determine "2x faster" but this doesn't seem like much of an improvement.
Click to expand...

Could be the overall speed that the processor is running also instead of 1.3ghz it could be running at 1.6ghz thus runs 31% faster claim just a theory
 
Intell said:
Even if the new iPhone has only 1GB of ram, there would be massive improvements to iOS' already great memory handling. In a 32-bit UNIX OS, every process needs to share the same 4GB virtual memory address space that is owned by the kernel. In a 64-bit OS, each 64-bit process gets its own 16TB virtual memory address space. While 32-bit processes still have to share the kernel's 4GB virtual address. This leads to much faster processing as 64-bit processes don't need to go through the kernel to process as much information.
Click to expand...

Color me...skeptical. There are plenty of processors that can do memory space isolation on a 32-bit processor; that's hardly something 64-bit specific. It's kind of moot, though. I can't see processes swapping out to flash any time soon without some major advancements in wear leveling. If physical RAM is all you have to work with most of the benefits of a larger memory space go out the window. The ability to overcommit is about all you've got left.
 
KPOM said:
64-bit seems unlikely since it would require a complete re-write of the iOS kernel, and existing 32-bit applications would need to be run in emulation. Wouldn't we have seen some signs in the developer toolkit if it were 64-bit?
Click to expand...
Unless iOS is already written so that it can be compiled for both architectures (it would make sense from a forward-thinking perspective). But yes, 32-bit apps would need to run in emulation mode, not that the performance impact use to be noticeable, really. But the performance benefits from going 64-bit is often not noticeable either! Surely not for Instagram or Flipboard! So I'm also doubting this. Sure, it makes sense with desktops requiring 8 GB RAM and more, but I don't think phones are going to have an architectural problem this soon. And besides lifting the RAM roof, we aren't really speaking of huge benefits. iPhones aren't known to run CPU intensive apps like rendering farms or Matlab...
 
bearda said:
Color me...skeptical. There are plenty of processors that can do memory space isolation on a 32-bit processor; that's hardly something 64-bit specific. It's kind of moot, though. I can't see processes swapping out to flash any time soon without some major advancements in wear leveling. If physical RAM is all you have to work with most of the benefits of a larger memory space go out the window. The ability to overcommit is about all you've got left.
Click to expand...

This isn't about memory isolation nor about swap. This is about virtual memory, not Windows virtual memory, but UNIX virtual memory. Go read up on the difference and how it works. Stop thinking about things in terms of Windows when discussing iOS.
 
teknikal90 said:
This is crap.
Apple is banking 50% of its revenue, on a 30% speed bump??
At a time when the market is like red hot with competitors with various innovations??
Click to expand...

What innovations? Nobody's done real innovating in the mobile space for a while. I'd rather a power-sipping A7 than Samsung's octa-core marketing crap.
 
zbarvian said:
What innovations? Nobody's done real innovating in the mobile space for a while. I'd rather a power-sipping A7 than Samsung's octa-core marketing crap.
Click to expand...

But you don't get it... they have 8 cores.

That's magical.

AND more cores means it will work better...
 
KPOM said:
64-bit seems unlikely since it would require a complete re-write of the iOS kernel, and existing 32-bit applications would need to be run in emulation. Wouldn't we have seen some signs in the developer toolkit if it were 64-bit?
Click to expand...

Don't forget that the iOS kernel is adapted from the OS X kernel, which was optimized to 64-Bit fairly easily. Plus it's not that hard to believe that Apple would be ok with running 32-Bit applications in a native emulation function for the time being. Maybe the GM will include the emulation or the 64-Bit 1st party applications. Also remember that each model of each device has its own ISPW file. It may not play well with the beta system to include 64-Bit functions on 32-Bit devices.

Also I'd like to add that if this is a 31% boost in clock speed (to 1.7-1.8 Ghz), that combined with the 64-Bit enhancements will make for a significantly faster FEEL for the phone. Everything will be buttery smooth and will also offer quite a bit of extra processing power.
 
Last edited:
KPOM said:
64-bit seems unlikely since it would require a complete re-write of the iOS kernel, and existing 32-bit applications would need to be run in emulation. Wouldn't we have seen some signs in the developer toolkit if it were 64-bit?
Click to expand...

Plus one
 
KPOM said:
64-bit seems unlikely since it would require a complete re-write of the iOS kernel, and existing 32-bit applications would need to be run in emulation. Wouldn't we have seen some signs in the developer toolkit if it were 64-bit?
Click to expand...

Read up on how ARM is going "64-bit", sir. The ARM v8 architecture is 40-bit/48-bit initially, expandable for some day in the distant future to 64-bit, and is capable of executing both legacy 32-bit and "64-bit" code.

SilianRail said:
They should've just done 64bit on iOS from day 1. Obviously this day would come eventually. Intel and AMD had 64 bit processors in 2003-4.
Click to expand...

Dear lord. ARM processors capable of word sizes over 32-bit are just hitting the market this year, dude.
 
True I'm thinking they would beta test the 32bit version while simultaneously testing the 64bit version knowing all the apps would migrate over perfectly. Since all the updates have their own ipsw the 5s could be the first 64bit phone and no one would be the wiser from the code that's out there.
 
Rogifan said:
Speak for yourself. Who says this fingerprint technology will be useless in the long run? Or that fad of large screens will continue?
Click to expand...

a fingerprint scanner is a gimmick, a larger screen is not.

there are more people that want a larger screen than people who want a fingerprint scanner. this is a fact.
 
If the 64 bit processor is true than that would explain why all the animations etc are running so slow as we test iOS 7. A 64 bit processor would solve this problem
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back