Earlier quoted context omitted.
M4 and M5 are literally general purpose computing parts. Apple literally owns the most profitable general purpose computing platform with the iPhone.
The iPhone is anything but a general purpose computing platform. Apple actively prevents many purposes.
Arm's Cortex X925: Reaching Desktop Performance
91–100 of 169 posts
Re: Arm's Cortex X925: Reaching Desktop Performance
#92ARM designs are effectively paper launches. You get these press releases saying the new ARM matches Apple and AMD, but its years before you can buy a product with it. Google Pixels that came out in the fall are still on the X4, which was introduced in 2023. At this rate, Pixel 11 will launch with X925, which is an Apple A17/M3 tier core, when Apple is on the A20: https://wccftech.com/apple-a20-and-a20-pro-all-technol…
This is an article testing shipping hardware you can buy today.
Re: Arm's Cortex X925: Reaching Desktop Performance
#93Earlier quoted context omitted.
Why should it be? All he is saying: We currently have products in a similar product category (arm based desktop computers) that are widely used and have known benchmark scores (and general reviews) and it would make sense if I publish a new cpu for the same product category ("Reaching Desktop Performance" implies that) that I'd compare it to the known alternatives. In the end you can just run Asahi on your macbook, t…
Does Apple allow benchmarks on Asahi Linux?
Re: Arm's Cortex X925: Reaching Desktop Performance
#94Earlier quoted context omitted.
The C1 Ultra looks really powerful. 128 kb L1D cache on it's own is a ~10% IPC improvement that should let it pull firmly ahead of the x86 competition which is very stuck at 32kb due to the legacy 4k page size.
I'm sorry, I'm clearly missing something but why would page size impact L1 cache size?
Re: Arm's Cortex X925: Reaching Desktop Performance
#95Kind of weird to see an article about high-performance ARM cores without a single reference to Apple or how this hardware compares to M4 or M5 cores.
That would only matter (to me, at least) if those Apple chips were propping up an open platform that suits my needs. As things stand today, procuring an M chip represents a commitment to the Apple software ecosystem, which Apple made abundantly clear doesn't optimize for user needs. Those marginally faster CPU cycles happen on a time scale that anyway can't offset the wasted time fighting MacOS and re-building decade…
Re: Arm's Cortex X925: Reaching Desktop Performance
#96Earlier quoted context omitted.
The core they're talking about was released about two years ago. nvidia stuck it on their grace blackwell (e.g. DGX Spark) as basically a coordinator on the system. Anyway, here it is in GB10 form- https://browser.geekbench.com/v6/cpu/14078585 And here is a comparable M5 in a laptop- https://browser.geekbench.com/macs/macbook-pro-14-inch-2025 M5 has about a 32% per core advantage, though the DGX obviously has a much…
Afaict the "desktop" target is meaningless these days. Desktops aren't really a thing anymore in the general sense are they? Only folks I know still hanging on to desktop hardware are gamers and even those I see going by the wayside with external video cards becoming more reliable. "Daily driver" is probably a better term, but everyone's daily usage patterns will vary. I could do my day job with a VT100 emulator on a…
Re: Arm's Cortex X925: Reaching Desktop Performance
#97Earlier quoted context omitted.
I don't think that's the primary reason there's momentum there. The reason is to avoid ARM licensing fees and IP usage restrictions. I think you'll see ever more accelerating RISC-V adoption in China if the United States continues on its "cold war" style mentality about relations with them. That said we're a long long way from Actually Existing RISC-V being at performance parity with ARM64, let alone x86.
Yep, licensing fee and IP usage restrictions is a massive decision point on some silicon markets. The other massive point: RISC-V integrates a lot of CPU "we know now" in a very elegant "sweet spot". And it is not china only, the best implementations are US, and RISC-V is a US/berkley initiative re-centered in switzerland for "neutrality" reasons. If good large RISC-V implementations do reach TMSC silicon process (5G…
Re: Arm's Cortex X925: Reaching Desktop Performance
#98Earlier quoted context omitted.
I'm sorry, I'm clearly missing something but why would page size impact L1 cache size?
This the the most cursed part of modern cpu design, but the TLDR is that programs use virtual addresses while CPUs use physical addresses which means that CPU caches need to include the translation from virtual to physical adress. The problem is that for L1 cache, the latency requirement of 3-4 cycles is too strict to first do a TLB lookup and then an L1 cache lookup, so the L1 can only be keyed on the bits of ram wh…
Re: Arm's Cortex X925: Reaching Desktop Performance
#99Earlier quoted context omitted.
The C1 Ultra looks really powerful. 128 kb L1D cache on it's own is a ~10% IPC improvement that should let it pull firmly ahead of the x86 competition which is very stuck at 32kb due to the legacy 4k page size.
I'm sorry, I'm clearly missing something but why would page size impact L1 cache size?
To do this lookup in the first place, you pull a number of bits from the virtual/physical address you're looking up, which tells you what bucket to start at. The minimum page size determines how many bits you can use from these addresses to refer to unique buckets. If you don't have a lot of bits, then you can't count very high (6 bits = 2^6 = 64 buckets) -- so to increase the size of the cache, you need to instead increase the associativity, which makes latency worse. For L1 cache, you basically never want to make latency worse, so you are practically capped here.
Platforms like Apple Silicon instead set the minimum page size to 16k, so you get more bits to count buckets (8 bits = 256 buckets). Thus you can increase the size of the cache while keeping associativity low; L1 cache on Apple Silicon is something crazy like 192kb, and L2 (for the same reasons) is +16MB. x86 machines and software, for legacy reasons, are very much tied to 4k page size, which puts something of a practical limit on the size of their downstream caches.
Look up "Virtually Indexed, Physically Tagged" (VIPT) caches for more info if you want it.
Re: Arm's Cortex X925: Reaching Desktop Performance
#100ARM designs are effectively paper launches. You get these press releases saying the new ARM matches Apple and AMD, but its years before you can buy a product with it. Google Pixels that came out in the fall are still on the X4, which was introduced in 2023. At this rate, Pixel 11 will launch with X925, which is an Apple A17/M3 tier core, when Apple is on the A20: https://wccftech.com/apple-a20-and-a20-pro-all-technol…
> ARM designs are effectively paper launches. You get these press releases saying the new ARM matches Apple and AMD, but its years before you can buy a product with it. This is an article testing shipping hardware you can buy today.