Qualcomm Employee: Apple's 64-Bit A7 Chip 'Hit Us In The Gut'


Recommended Posts

Source: http://www.macrumors.com/2013/12/16/qualcomm-employee-64-bit-a7-chip-hit-us-in-the-gut/

 


"The 64-bit Apple chip hit us in the gut," says the Qualcomm employee. "Not just us, but everyone, really. We were slack-jawed, and stunned, and unprepared. It?s not that big a performance difference right now, since most current software won?t benefit. But in Spinal Tap terms it?s like, 32 more, and now everyone wants it."

[...]

"The roadmap for 64-bit was nowhere close to Apple?s, since no one thought it was that essential," the Qualcomm insider says. "The evolution was going to be steady. Sure, it?s neat, it?s the future, but it?s not really essential for conditions now."

But once Apple introduced a 64-bit processor, all the other phone-makers wanted one too. "Apple kicked everybody in the balls with this. It?s being downplayed, but it set off panic in the industry."

Basic psychology of want, not because I need, but because I want. Eg. I want what he has, just cause I don't have it.

 

Its like most analyst said: 64-bit makes little-to-no-difference but you can bet money that all the flag ship Android phones next year are going to be sporting it in response to Apple.

Its like most analyst said: 64-bit makes little-to-no-difference but you can bet money that all the flag ship Android phones next year are going to be sporting it in response to Apple.

 

This. If anyone argues so much about who does it first who does it right on here when it comes to Apple vs Android, it's me. Just like every release of an iDevice, how many Android devices have you seen try to follow a feature right after? HTC Fingerprint for example. Apple may not have done the fingerprint first, but they did it right which made others attempt to follow.

  • Like 1

Its like most analyst said: 64-bit makes little-to-no-difference but you can bet money that all the flag ship Android phones next year are going to be sporting it in response to Apple.

Pretty much.

 

Sad that when everyone else points out how useless at the moment 64 bit makes in smartphone OSes, they get bashed.

I can see that. Apple touted 64-bit goodness as a major selling point, and relevant or not, if other smartphones don't have 64-bit processors, they'll all be have-nots.

  • Like 2

It is the same old thing again. This situation is like, when you have two balls which look exactly the same and you will need the heavier in the future. Your friend drops the balls from a skyscraper and you are waiting for them on the ground. At this moment, as technology goes, the balls are still falling and there is no difference between them, but when they hit the ground and the software will begin to harness the benefits of 64 bit technology, you will need the heavy stuff.

 

Apple, yet again, tried to flash its E-penis and painted the ball red. Now everyone wants a falling red ball even if it does not matter. How easily distractable customers are. 64 bit is twice as much as 32, it must be soooooooooooo much better!

  • Like 1

It's hard to quantify just how much this will matter in a year or two. When AMD introduced 64-bit desktop CPUs it wasn't "needed" either but it jump started the industry and competition and soon after it was a necessity. 

  • Like 1

Basic psychology of want, not because I need, but because I want. Eg. I want what he has, just cause I don't have it.

Some of that is at play yes, but technology is also a chicken or egg industry...

 

What should come first? Software that needs 64bit or chips that support 64bit? See the conundrum?

 

Usually software waits for the hardware to exist before they start exploiting it. So the sooner we get 64bit hardware the sooner we'll get applications that take advantage of it. We can't accurately say if the advances will be useful or not yet because we don't yet have them...

Its like most analyst said: 64-bit makes little-to-no-difference but you can bet money that all the flag ship Android phones next year are going to be sporting it in response to Apple.

 

Samsung already announced 64bit.  But this is normal no matter what industry you work in.  Someone produces something, others find value and add it to their products.

Its like most analyst said: 64-bit makes little-to-no-difference but you can bet money that all the flag ship Android phones next year are going to be sporting it in response to Apple.

and then Windows Phone will be reviewed poorly for using "only" 32bit processors. :laugh:

This. If anyone argues so much about who does it first who does it right on here when it comes to Apple vs Android, it's me. Just like every release of an iDevice, how many Android devices have you seen try to follow a feature right after? HTC Fingerprint for example. Apple may not have done the fingerprint first, but they did it right which made others attempt to follow.

My Motorola Atrix finger print worked fine.  2 years before the iPhone 5.

  • Like 3

My Motorola Atrix finger print worked fine.  2 years before the iPhone 5.

 

I don't think his point was that Apple came out with a fingerprint reader on their phone first.  His point was that your Motorola Atrix introducing the feature didn't mean squat to other Android manufacturers.  Once Apple released the iPhone 5S with a fingerprint reader there was a sharp 'me too' response almost immediately from the Android OEMs.

  • Like 2

Even quad cores are overkill.  64 bit is getting ready for when phones need more then 4 gigabytes in memory. 

You do realize that 64-bit has more advantages than just memory capacity, right?...

  • Like 1

I'm not an Apple fan at all. I hate their "Walled Garden" and one size fits all designs but I have to hand it to them. I'd love an A7 SoC in a phone I actually liked.

As for those saying 64bit doesn't make a difference it's true there isn't much, if any improvement (in some cases things may even slow down) simply by going 32bit to 64bit. The ARMv8 architecture isn't just an ARMv7 with 64bit tacked on though and it DOES have substantial speed improvements even when running just 32bit software. ARM really took this opportunity to clean up and fine tune their design and it paid off.

Apple really is ahead of the game in SoC design and 64bit OS support (their entire OS and all it's built-in apps have 64bit versions already) so that's a big win for them. They need it though because iOS apps are native code and everything needs to be recompiled to support 64bit. That's going to be a HUGE and long transition for them. In contrast since Android and Windows Phone compile to byte-code unless developers wrote parts in native code (NDK on Android, not sure if Windows Phone has an equivalent) they have to do nothing. The 64bit JIT engine provided by the OS will automatically compile their byte-code application 64bit. This means the migration to 64bit will take much less time on Android/Windows Phone so it's good Apple has a head start to stay competitive (competition is good for us consumers)

I'm not an Apple fan at all. I hate their "Walled Garden" and one size fits all designs but I have to hand it to them. I'd love an A7 SoC in a phone I actually liked.

As for those saying 64bit doesn't make a difference it's true there isn't much, if any improvement (in some cases things may even slow down) simply by going 32bit to 64bit. The ARMv8 architecture isn't just an ARMv7 with 64bit tacked on though and it DOES have substantial speed improvements even when running just 32bit software. ARM really took this opportunity to clean up and fine tune their design and it paid off.

Apple really is ahead of the game in SoC design and 64bit OS support (their entire OS and all it's built-in apps have 64bit versions already) so that's a big win for them. They need it though because iOS apps are native code and everything needs to be recompiled to support 64bit. That's going to be a HUGE and long transition for them. In contrast since Android and Windows Phone compile to byte-code unless developers wrote parts in native code (NDK on Android, not sure if Windows Phone has an equivalent) they have to do nothing. The 64bit JIT engine provided by the OS will automatically compile their byte-code application 64bit. This means the migration to 64bit will take much less time on Android/Windows Phone so it's good Apple has a head start to stay competitive (competition is good for us consumers)

 

I used to think Android apps were less native due to the fragmentations and whatnot. It may be quicker, but it'll still be hard to get it to roll out on all the devices out there like Apple can.

I used to think Android apps were less native due to the fragmentations and whatnot. It may be quicker, but it'll still be hard to get it to roll out on all the devices out there like Apple can.

Android apps are "less native" so the same app can run on multiple different architectures. This is why you can have an app that runs on an ARM based phone as well as an Intel based one (completely different architecture). More new ones are even on the way with Imagination Technologies (people who make the PowerVR GPUs used by Apple and others) having bought MIPS expect to see devices running MIPS/PowerVR SoCs in a 2014/2015. Google does it this way because they don't make their own hardware and they want to be able to use whatever is best at any given moment and not be stuck to one architecture. It works in their favor for the 32 to 64 bit transition as well. The hard work is done in the JIT compiler provided by the OS instead of every app having to be recompiled. That work is typically done by the hardware manufacturers, for example Intel has been checking in a lot of code to the Android codebase to get 64bit working on their processors. Once that is complete any OEM making an android phone with an Intel SoC will use the Intel provided JIT compiler and app developers will have to do nothing. The exception being if the app uses the NDK (native development kit) in which case it has architecture specific native code and the app developer will need to recompile the NDK parts for every architecture they wish to support (just as Apple app devs will have to).

On a side note Android is also making a AOT (Ahead of Time) compiler called ART (Android Run-Time) to replace the Dalvik JIT engine so that apps compile from byte code to native code on install instead of on run. If you are familiar with .Net this is similar to the NGEN tool that .Net has which apps like Paint.Net use on install.

So you are saying that 64-bit is more useful with 512MB memory as a whole, than 32-bit with 2GB memory?

Uh...where are you drawing that conclusion from?  The point is that the amount of memory doesn't matter.

Yes, you can use more than 3.5GB of memory with 64-bit, but that's only one of many advantages.

A major benefit is security.  

 

Educate yourself on why a 64-bit instruction set is very beneficial.  There's a lot of information out there.

Apple leads the way....once again.

I wouldn't say leading, as it would if ATM it were a meaningful advantage, like pointed above, 64 IS the future, but in 2-3 years. Heck we've barely transitioned into 64 bit on desktops.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • NASA: This asteroid may not kill us but it probably won't be far off either by Sayan Sen Image by Zelch Csaba via Pexels New observations by NASA's James Webb Space Telescope have eliminated the last remaining impact threat posed by asteroid 2024 YR4, ruling out the possibility that the near-Earth object could strike the Moon in December 2032. NASA said observations collected by Webb on February 18 and 26, 2026, enabled scientists to refine the asteroid's orbit enough to "rule out a chance of lunar impact on Dec. 22, 2032." Instead, asteroid 2024 YR4 is now expected to pass the Moon at a distance of about 13,200 miles (21,200 km). The agency stressed that the update "reflects improved precision in our understanding of where the asteroid is expected to be in 2032 rather than a shift in its orbital path." The announcement closes a remarkable chapter in planetary defence that began in late 2024, when the approximately 60-metre-wide asteroid briefly became the most closely watched near-Earth object in the world. Discovered on December 27, 2024, by the ATLAS telescope in Chile, 2024 YR4 initially appeared to have a small chance of colliding with Earth on December 22, 2032. As astronomers gathered more observations, the impact probability briefly climbed to around 3%—the highest ever recorded for an asteroid of its size—before steadily falling as its orbit became better understood. By early 2025, international observations had ruled out any significant risk to Earth. However, astronomers were left with another possibility: a roughly 4% chance that the asteroid could instead strike the Moon. "The probability that asteroid 2024 YR4 will strike the Moon on 22 December 2032 is now approximately 4%," the European Space Agency (ESA) had said last year, noting that "there is a 96% chance that the asteroid will not impact the Moon." ESA said such an impact, while unlikely, would have presented an extraordinary scientific opportunity. "It is a very rare event for an asteroid this large to impact the Moon – and it is rarer still that we know about it in advance. The impact would likely be visible from Earth, and so scientists will be very excited by the prospect of observing and analysing it," said Richard Moissl, Head of ESA's Planetary Defence Office. "It would certainly leave a new crater on the surface. However, we wouldn't be able to accurately predict in advance how much material would be thrown into space, or whether any would reach Earth," he added. The asteroid also exposed an important blind spot in planetary defence. Because 2024 YR4 approached Earth from the direction of the Sun, it remained hidden from ground-based telescopes until after its closest approach. "We looked into how Neomir would have performed in this situation, and the simulations surprised even us," Moissl said. "Neomir would have detected asteroid 2024 YR4 about a month earlier than ground-based telescopes did. This would have given astronomers more time to study the asteroid's trajectory and allowed them to much sooner rule out any chance of Earth impact in 2032." He added, "As an infrared telescope, like Webb, Neomir would have also immediately given us a much better estimate for the asteroid's size, which is very important for assessing the significance of the hazard." The latest NASA observations underscore the value of space-based infrared telescopes in tracking faint asteroids. According to NASA, Webb made "among the faintest ever observations of an asteroid," extending the object's observational record by nearly eight months at a time when it had become too faint for other telescopes. That additional data allowed scientists to eliminate the remaining uncertainty surrounding its 2032 flyby. Although asteroid 2024 YR4 is now confirmed to pose no threat to either Earth or the Moon, scientists say its discovery remains one of the most significant real-world tests of the international planetary defence system, demonstrating how continued observations can rapidly transform an object once considered hazardous into one whose future path is known with high confidence. Source: NASA, ESA This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Yup. Google is just scraping the entire internet for their own ad profits without sharing revenue with the sources. It's obviously stealing, but since these sites depend upon Google's search scraps to survive... As for me, I just stopped using Google for anything except Reddit searches. If Reddit's own search wasn't complete crapola, I'd never use Google search again.
    • I had a feeling this was coming. Picked up my first Mac ever last Saturday. Glad I did.
    • In a major surprise there is actually some good deals for the first time in years. At least for me.
  • Recent Achievements

    • Conversation Starter
      Admir earned a badge
      Conversation Starter
    • First Post
      The_Focal_Point earned a badge
      First Post
    • Apprentice
      daryld went up a rank
      Apprentice
    • Contributor
      Carltonbar went up a rank
      Contributor
    • One Month Later
      The_Focal_Point earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      419
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      130
    4. 4
      Xenon
      69
    5. 5
      neufuse
      69
  • Tell a friend

    Love Neowin? Tell a friend!