You are not looking at the available facts
You have a number of serious misconceptions
- Apple CPUs most likely have higher IPC than A64X or other HPC chips
A conjecture. Again, scaling to large core counts necessarily decreases effective IPC due to bandwidth constraints and memory latency going way up. Intel has the same problem.
Again, you have to do a lot of work to make sure the IO system can feed the same cores. This is why it's not an issue of pasting 64 iPhone cores together. A ton of engineering needs to happen.
- HPC or server chips have ultimately a completely different performance profile than a workstation. They are optimized for parallel throughout while a workstation needs to support hybrid asymmetric workloads
Wrong. You can see this on Intel. The instruction latency and pipelines on the world's fastest Xeon supercomputer are identical to that of the Macbook Air. Same core.
You are imagining somehow the architecture changes. It does not. Everything around the core changes, which is what I've been repeatedly saying.
You don't understand large CPUs. It's never a core issue, its an I/O issue.
- Apple CPUs implement a later ARM ISA different standard than A64X. Apple CPUs contain custom ISA extensions (AMX). Finally, I am sure that Apple CPUs contain specialized instructions to support Rosetta 2. You can’t just modify an A64X to include all that. And Apple wouldn’t choose to fragment their own hardware where they have the chance - for the first time ever - to
unify its capabilities
Wrong. ARM is notoriously strict about binary compatibility. You cannot touch the ISA. As I said, Apple's accelerators are a CEVA block outside the CPU. That's like saying an Nvidia GPU on a computer is somehow affecting the Intel ISA.
And they've already "fragmented" their ISA. Sort of how iPhone 11 programs don't run on the iPhone 7, you know since there's huge binary incompatibilities. Oh wait...
- finally, again: the Mac Pro does not have to be profitable. It’s a show off product. The PR and indirect revenue will more than offset the cost of chip design
I'm saying the Mac Pro needs to not cost 3x it's price, which is what you're suggesting by having Apple engineer its own large core count CPU. People already complain about how much the wheels cost.
[automerge]1595833787[/automerge]
The point is, dual CPU boards have existed a long time and Apple has had a decade or more to work on this hardware. Claiming they can't do something because "its hard" is just as wild a guess at this point. They've overtaken the industry leaders in that time for performance and power consumption.
I never said they can't. I said it's too expensive and a distraction for a niche product. Especially when they can buy.
Apple has not made a dual socket Mac since 2012.
You're saying it's cheap and easy. The whole industry says it's not.
According to the documentation, your USB T2 is actually a coprocessor so there's clearly some meshing going on there.
Apple marketing for fanboys. Apple documented how it acts. It's a USB device and SPI.