Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
32 bit land is dead.

I can see Apple dropping all 32 bit support in less than 4 years. By that time they can implement straight AArch 64 and drop all the cruft 32 bit hardware. Why would they do this? Simple to save power and transistors.
 
And people said 64-bit was useless in a mobile phone. :rolleyes:

Yep the 64-bit sure looks like a gimmick to me. The rally cry, "64-bit only matters when using more then 4GB of RAM" :rolleyes:

Pretty amazing considering the A7 has been reported to be a 1.29GHz dual core processor.

----------

So much for all those idiots decrying 64-bit as nothing more than the ability to address more system memory. I swear. If Samsung had released a 64-bit chip, it would have been the most awesome thing ever according to the tech media, but when Apple releases a chip that is truly a leap in performance, the tech media acts like it's no big deal. I remember all those Android talking heads barking about how fantastic the Exynos 5 was going to be, and how they fell suspiciously silent when the North American version of the phone shipped without it.

+1 Exactly.
 
Those who understand just a bit about computing and OS concepts know that the change of architecture to 64 bit is a huge leap. Those who don't know what the hell they're talking about would say it's a gimmick.
 
For the realtime video-mixing app Vjay, the most processor-intensive task has always been decoding two videos simultaneously.

...

With the iPhone 5s and the 64-bit A7 processor, decoding speed is twice as fast as before, and the iPhone 5s can process two full 720p HD video streams. The app can also export HD video over AirPlay in real time with zero latency.
Faster video decoding & encoding (including AirPlay) has nothing to do with the 64-Bit CPU registers and instructions. Mobile devices use special decoder and encoder units for such tasks.

Here is an example:
ARM Ltd. said:
From:
http://www.arm.com/products/multimedia/mali-video/mali-v500.php


Why Mali-V500?

Building on the strong momentum and expertise of ARM Mali’s graphics solutions, the Mali-V500 offers a scalable, secure solution to the video processor market capable of 4k resolution at 120fps on eight cores; thanks to this “trick-play,” video edit and slow motion capture in HD is consequently possible. Even with a single core, the Mali-V500 is capable of bringing 1080p60 performance to mass-market smartphones, accordingly meeting growing consumer expectations and changing video consumption patterns. The design is capable of managing multiple, simultaneous encode and decode HD streams and through this can support multi-party video conferencing and advanced user interfacing.

Even on the Mac platform Apple uses Intel Quick Sync for the realtime en- and decoding of H.264 HD streams (AirPlay). The 64-Bit CPUs at least in Macs can do this too (for example via AirParrot), but they are less efficient than the Quick Sync video en-/decoder. Mobile devices with ARM processors have the same problem. The CPU is too inefficient for video en-/decoding.
 
So much for all those idiots decrying 64-bit as nothing more than the ability to address more system memory. I swear. If Samsung had released a 64-bit chip, it would have been the most awesome thing ever according to the tech media, but when Apple releases a chip that is truly a leap in performance, the tech media acts like it's no big deal. I remember all those Android talking heads barking about how fantastic the Exynos 5 was going to be, and how they fell suspiciously silent when the North American version of the phone shipped without it.

----------



64 bits lets you handle some pretty big integers natively.
I think you have it in reverse. If anybody else had created a 64 bit chip, people like you would be decrying that its nothing but useless hardware spec used for bragging and that its all about the user experience. But when apple does it, its amazing and a game-changer.
 
This is exactly why 64-bit is such a huge deal...
No. The 32-Bit OS X kernel (darwin) supported > 4 GB RAM without a problem, and apps (like the 32-Bit version of HandBrake) used 128-Bit instructions and registers via SSE2 (and newer) in the past on 32-Bit CPUs. The current Haswell platform supports 256-Bit instructions & registers via AVX2.

Apple has already begun to merge OS X & iOS
No.

Read:
MacRumors said:
From:
https://www.macrumors.com/2012/12/0...driven-by-desire-for-increased-collaboration/

“Cook is careful to note, however, that this increased collaboration is not working toward a merger of iOS and OS X as some have speculated.”

Tim Cook said:
We don’t subscribe to the vision that the OS for iPhones and iPads should be the same as Mac. As you know, iOS and Mac OS are built on the same base. And Craig has always managed the common elements. And so this is a logical extension. Customers want iOS and Mac OS X to work together seamlessly, not to be the same, but to work together seamlessly.

...and now with 64-bit chipsets in the iPhone...
We talk about CPUs, not about chipsets.

...developers will be able to make essentially one app for them all!
No, it is not that easy.
 
…..He told us that the Djay and Vjay programming teams were able to 64-bit compatible versions of the apps just three days after the iPhone 5s went on sale largely because of Apple's excellent developer tools.

The teams use a shared codebase between Algoriddim's iOS and Mac apps, and code that had been written previously for the 64-bit versions of the Mac apps was able to be transitioned to iOS with a relatively minimal amount of effort. They were able to get 64-bit versions running in the Xcode iOS simulator and when the iPhone 5s hardware was released on Friday, the team was able to get a version of the software -- complete with new iPhone 5s-only features -- ready for a public release on Monday.

Morsy explained that because Apple's Xcode tools allow code to be moved from desktop to mobile, its development cycle was dramatically shortened. "Anything we develop on one platform, the code can be reused on other platforms," Morsy told MacRumors. "Our strength is a code base shared across three platforms, and it's a key reason we are successful on Apple's app ecosystem."

Article Link: Djay and Vjay Updated for iPhone 5s, 64-Bit A7 Processor 2-4 Times Faster for Some Tasks

I see a wave of awesome new apps coming in the not too distant future, all taking full advantage of this 64-bit architecture, in the --for now-- industry leading A7+M7 combination. It's even harder to realize that all this fits in the palm of your hand.
 
I feel its more important to note that Apple makes some of the most awesome developer tools. It isn't exactly easy to move code between desktop and embedded platforms, or transition to 64-bit, especially for games/apps that use low level frameworks like OpenGL.

With Apple, it was a breeze when OS X 10.6 came out and now with the iPhone 5s/iOS 7. You can compare this to the driver/software compatibility woes of Windows Vista x86-64 :)
 
Of course you have to purchase the update

They said how easy it was to create the update and yet you have to pay for it again even if you just bought the previous version.

It is a great app when it works, however people should be aware that it will not work if you are using iTunes Match.
 
According to Anandtech's iPhone 5S review, one of the strength of a 64-bit CPU over 32-bit is compression/decompression performance. Since MP3s are highly compressed it makes sense that loading them is quicker.

The biggest performance increase however is with encryption, particularly with AES which gives a speed boost of over 8x compared to 32-bit, pretty crazy.

I am not one of those who says 64-bit is just a gimmick/marketing move. However, faster encryption and decryption is due to new cryptography instructions in the ARMv8 - not the 64-bit CPU.

----------

I can see Apple dropping all 32 bit support in less than 4 years. By that time they can implement straight AArch 64 and drop all the cruft 32 bit hardware. Why would they do this? Simple to save power and transistors.

And to save development time for themselves and third parties...

----------

I think you have it in reverse. If anybody else had created a 64 bit chip, people like you would be decrying that its nothing but useless hardware spec used for bragging and that its all about the user experience. But when apple does it, its amazing and a game-changer.

It is all about performance and user experience. 64-bit is important, it's a change in architecture. More GHz and Cores? Not very impressive.
 
Just want to point out that the a7 is using the new armv8 instruction set that is by default up to 35% faster then the last gen armv7 and apple also went from 1.3ghz to 1.7ghz

Run the same app on the new a7 in 32 bit vs 64 bit and the results will be within 3-5% of each other.
 
It appears as though it is now Djay 2, not an update to Djay. So for those of us that paid for the original app, we're no longer supported? That's F-in lame.
 
I think you have it in reverse. If anybody else had created a 64 bit chip, people like you would be decrying that its nothing but useless hardware spec used for bragging and that its all about the user experience. But when apple does it, its amazing and a game-changer.

The only publication I've read that didn't shrug off the A7 as nothing special was The Verge.

The truth is that Apple has embraced the much more efficient Arm v8 instruction set, while I imagine that Samsung's foray into 64 bit will likely still be using the BIG little instruction set which is akin to Intel's chasing MHz with the old NetBurst design while AMD sought efficiency and parallelism.
 
Faster video decoding & encoding (including AirPlay) has nothing to do with the 64-Bit CPU registers and instructions. Mobile devices use special decoder and encoder units for such tasks.
...

Even on the Mac platform Apple uses Intel Quick Sync for the realtime en- and decoding of H.264 HD streams (AirPlay). The 64-Bit CPUs at least in Macs can do this too (for example via AirParrot), but they are less efficient than the Quick Sync video en-/decoder. Mobile devices with ARM processors have the same problem. The CPU is too inefficient for video en-/decoding.

Source? Someone said this too, but according to the article, it's the 64-bit CPU doing the heavy lifting. If there's a separate unit doing all the heavy-lifting for encoding/decoding video/audio, why is what's described above not possible with, say, iPhone 5?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.