Oh, SPEC results for M4 are already there. Geekerwan posted a video (for now in Chinese). It is being discussed at Anandtech forums.
Page 274 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
forums.anandtech.com
I noticed in that thread that someone also linked to an old rant about IPC that makes mine look ... moderate - i.e. that IPC should only be measured for precise sections of code never mind specific workloads. Probably true. He also talks about how indeed some algorithms are intrinsically low IPC, you simply aren't going to get around that no matter how smart your silicon designers are.
@Jimmyjames you might find this interesting.
Lately some of our forum members have expressed divergent opinions on how IPC should be measured and interpreted in the context of systems with different power and clock targets. This thread is intended to be the right place for opinions this matter, whether derived from experience or based on...
forums.anandtech.com
What I find really galling is when blue-check tech enthusiast posted a quote tweet of the the original tweet
@Jimmyjames found, where he was preemptively upbraiding Youtube tech personalities for just mindlessly posting how Apple's M4 was going to be good because of the GB 6 score without understanding why and how the tweet
@Jimmyjames found proved Apple were actually at a standstill. But they themselves don't actually understand the concepts at play either. There is no singular IPC value. Even what
@leman and I did is more akin to clock normalized single threaded comparison, though at least we tried to use the available data we had to make it as specific to the workload as possible - again, we have the data we have.*
Edit: Here's the tweet:
twitter.com
Of course he also got that GB6 doesn't support AMX wrong ... and never even discussed the impact of AVX-512. And stated that no one will use it because the GPU and NPU exist ... sigh ... those will sometimes be too busy and too heavy for what's needed and the workload is better suited to an accelerator closer to the CPU, lower latency, lighter weight, and not occupied. That's why those accelerators exist, it's why Intel, AMD, Apple, and a host of other silicon design companies burn precious silicon on them. Gah! And it's not all AI workloads though that's the obvious current hotness.
EDIT2: *I should also point out that
@leman used the correct term - iso-clock performance gains in his graph, I (mis)-used the term IPC in my chart and graph. Because those enthusiast tech guys who don't actually know anything? That'd be me too.
EDIT3: I have to be honest: I don't really have a problem with using IPC in a more colloquial manner ... but if someone's going to make statements about how ignorant other people are, they had better have their own ducks in a row. I know I'm not an expert either and I am also currently shitting on someone from on high right now. So I get the hypocrisy, I'm doing the same thing. But at least I guess I just rant on here to you guys ... and occasionally Macrumors.
Okay I'll stop digging now ...