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


Recommended Posts

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.

 

It's the future now. 

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.

That statement doesn't even make sense. When the first HD televisions were introduce, you "wouldn't say" they were leading the way simply because no HD content were available at the time? You can't make HD content if they aren't TVs around to play them on. And it isn't a chicken a egg problem as stated earlier. The hardware has always come first. Resources are limited; It simply makes no financial sense to write and deploy software for hardware that isn't available. In Xcode, you couldn't even compile iOS apps into a 64 bit binary until recently anyway, even if you wanted to. The A7 will be the reason we'll soon see 64-bit computing become mainstream. That is a reason to say it is leading.

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.

 

4GB, not 3.5GB (It'll be 3.5GB if you have something like a 512MB graphics card, a 1GB one will give you 3GB usable, etc.)

 

And ASLR is useful, but it's not like 32bit can't do it, 64bit just makes it harder to brute force (Most times you'll break ASLR via other means)

The A7 will be the reason we'll soon see 64-bit computing become mainstream. That is a reason to say it is leading.

 

What a ridiculous thing to say...  A measely little mobile processor is NOT the 64bit evangelist you think it is. Intel and AMD are already there and have been for years; Microsoft are the ones making it mainstream as their OS is the market driver.

  • Like 2

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.

 

What is beneficial for security in ARM's A64 ISA? I know ARMv8 has crypto instructions but those are available in both the 32-bit and 64-bit variants.

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.

 

I don't want to turn this into another apple vs android debate, but apple has been a little lagging in some areas compared to others, why I don't know, but some features becoming available to apple phones, have been around since the '90's, anyone with an old Symbian Nokia could stand up and say, well we had video calling on my Nokia 6630, or some other thing, fingerprint scanners were available on Eurocom Panther laptops since win 7 launch.

 

I'm not an apple hater because I have an android phone, I'm actually not a fan of android neither, but I am glad to see technology advancing.

Having said that, I do wonder, how much 'tech' does one actually need in any smartphone? I've said this in the past, I just don't get the need to have full blown tablet computers with a speaker, a mic and a sim port. (A little hypocritical of me I'll admit due to having a smartphone myself, but for me 6630 was close to perfect, and if I admit it, the N8, <my opinion the best Nokia Symbian ever made> was more phone than I needed.

 

That being said, Good for Apple, these advancements can lead to great devices elsewhere as well, (kinda like the existence of the rpi or some portable medical equipment)

Some of you guys kept saying how Apple is useless because the hardware was never raising the bar. I never heard any Android fanatic saying that multicore and ram-heavy phones were unnecesary.

 

Now that Apple released a 64 bit phone (Which, by the way, has more advantages than 'using more ram', like better proc instruction sets) some of you are saying that it's overkill.

 

Make your mind. 

Some of you guys kept saying how Apple is useless because the hardware was never raising the bar. I never heard any Android fanatic saying that multicore and ram-heavy phones were unnecesary.

 

Now that Apple released a 64 bit phone (Which, by the way, has more advantages than 'using more ram', like better proc instruction sets) some of you are saying that it's overkill.

 

Make your mind. 

If you're referring to me, please note, I was trying to tiptoe carefully in what is a potential minefield that is the apple vs android debate, I do not consider myself in either camp because as soon as ANY smartphone manufacturer decides to revive Symbian, I'll jump ship there and then.

If you're referring to me, please note, I was trying to tiptoe carefully in what is a potential minefield that is the apple vs android debate, I do not consider myself in either camp because as soon as ANY smartphone manufacturer decides to revive Symbian, I'll jump ship there and then.

 

Actually I'm not referring to anyone. I did a general read without looking at names and came to my conclussion.

  • Like 1

Some of you guys kept saying how Apple is useless because the hardware was never raising the bar. I never heard any Android fanatic saying that multicore and ram-heavy phones were unnecesary.

 

Now that Apple released a 64 bit phone (Which, by the way, has more advantages than 'using more ram', like better proc instruction sets) some of you are saying that it's overkill.

 

Make your mind. 

 

Well, in the defense of sane architecture, an ISA is mostly only as useful as the instructions you use or need. Throwing 64-bit instructions in is useless if you don't need the extended range provided by the numbers. The performance gains reported are most likely just the result of more registers being available and simply better scheduling as a result.

 

EDIT: anyone know if apple is bundling both 64-bit and 32-bit compiled codes in one executable like what is done for Osx (and should be done for windows...)?

Well, in the defense of sane architecture, an ISA is mostly only as useful as the instructions you use or need. Throwing 64-bit instructions in is useless if you don't need the extended range provided by the numbers. The performance gains reported are most likely just the result of more registers being available and simply better scheduling as a result.

 

EDIT: anyone know if apple is bundling both 64-bit and 32-bit compiled codes in one executable like what is done for Osx (and should be done for windows...)?

 

Without the source you can't tell for sure if ios7 is using or not using the extra instructions. But if what I got from the Infinity Blade III presentation video is correct then indeed there are both 32/64 compilations in one package and the ios installed on the 5s uses the extended instruction set.

Without the source you can't tell for sure if ios7 is using or not using the extra instructions. But if what I got from the Infinity Blade III presentation video is correct then indeed there are both 32/64 compilations in one package and the ios installed on the 5s uses the extended instruction set.

 

Did they say either universal or fat binary? Those are the two terms I know that mean that. I'd imagine they would be doing it because it is a particularly good idea.

Did they say either universal or fat binary? Those are the two terms I know that mean that. I'd imagine they would be doing it because it is a particularly good idea.

 Neither. Let me look for the video, but they said something a long the lines of "specific builds". I tend to believe it since the video was to show how better the 5s ran Infinity Blade III, something impossible if the os is not accessing the extended instruction set that the game is using.

Ummm, isn't the A7 chip based off of Qualcomm's technology?

 

As far as I know, it's all the contrary: The design was made by Apple with Samsung assistance and Samsung manufactured it.

Just wondered because many chip makers pay QUALCOMM royalties.

 

Nah, it is what sanctified said, Samsung manufactures their processors (well SoCs now). They used Cortex series chips for the 3 and 4 and standard samsung processors prior. They've never used qualcomm parts.

 

EDIT: looks like both the 5 and 5s use straight up apple designed processors, so they aren't licensed from anyone at all. The Cortex ones were licensed from ARM.

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.

You're talking about the amd64 instruction set, which indeed added security measures. However, this is ARM we are talking about, you can't just assume that 64 bit ARM will have the same advantages as x86-64.

 

In fact, you educated one, can you tell me the differences between the ARM 32 and ARM 64 instruction sets?

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

    • No registered users viewing this page.
  • Posts

    • finally [Taskbar] Taskbar customization just got easier. As we continue to make improvements to the Taskbar experience mentioned last month, we've introduced a dedicated Taskbar Size setting, making it simpler to find, understand, and personalize your ideal taskbar experience.
    • Let me get this straight... It was a web interface for Gmail, so if privacy at Google wasn't concerning enough you'd be going through two companies. And their big feature was the very thing that would make people consider dumping Gmail.
    • Microsoft's fast coding model MAI-Code-1-Flash comes to Copilot Business and Enterprise by Karthik Mudaliar Microsoft’s recently announced MAI-Code-1-Flash model is now generally available to GitHub Copilot Business and Copilot Enterprise customers. With this support, organizations can have more centralized policy controls and billing while finally being able to use Microsoft’s lightweight, first-party coding model. According to GitHub’s announcement, Business and Enterprise plan administrators must enable the MAI-Code-1-Flash policy in Copilot settings before developers can access the model. Microsoft says that MAI-Code-1-Flash is for fast, iterative coding work rather than the most demanding architectural or debugging tasks. GitHub’s official model comparison page says that the model is great for "general-purpose coding and writing," while it excels at fast, accurate code completions and explanations Microsoft introduced MAI-Code-1-Flash on June 2 as part of a broader collection of internally developed MAI models. GitHub subsequently expanded support to Copilot CLI, the Copilot cloud agent, GitHub.com chat, GitHub Mobile, Visual Studio, JetBrains IDEs, Eclipse, and Xcode, but said support for managed Business and Enterprise customers was still on the way. In Microsoft’s own benchmark testing, MAI-Code-1-Flash scored 51.2% on SWE-Bench Pro, compared with 35.2% for Anthropic’s Claude Haiku 4.5. Microsoft also claimed that the model used up to 60% fewer tokens on SWE-Bench Verified. Do note that these are vendor-run results rather than independent measurements. The model is billed at provider list pricing under GitHub’s usage-based system. GitHub currently lists MAI-Code-1-Flash at $0.75 per million input tokens, $0.075 per million cached input tokens, and $4.50 per million output tokens. For organizations, the main incentive to use MAI-Code-1-Flash is likely to be efficiency rather than maximum capability. A smaller model that responds quickly and limits unnecessary output is quite useful for repetitive agent tasks at scale, especially after GitHub Copilot’s move toward usage-based billing. The "Flash" model is recommended for fast work and not necessarily for huge repositories with loads of context. It's better if teams compare their output with other larger models, especially if they're working on security-sensitive changes and complex, multi-file work.
    • yes AND no the "original" or plain/normal Optiplex 7010 won't be getting any more new firmware updates BUT the Optiplex SFF/SFF Plus {small form factor}, Micro/Micro Plus & Tower/Tower Plus 7010 editions DO get new updates such as this new one   and here are similar guides from the Dell web site for Dell systems: https://www.dell.com/support/kbdoc/en-us/000390990/secure-boot-transition-faq https://www.dell.com/support/kbdoc/en-us/000347876/microsoft-2011-secure-boot-certificate-expiration
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      462
    2. 2
      +Edouard
      213
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      73
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!