[kllrnohj]

> It's not the exact same binary - that's the point

I think you misunderstood. "GNU Radio" on M2 was sometimes screamingly fast, and sometimes embarrassingly slow, depending on which test it was.

I'm not saying that "GNU Radio" was the same on M2 and AMD, obviously it's not. I'm saying the performance results for GNU Radio specifically were insanely inconsistent - M2 won by a stupidly huge amount in one of the GNU radio results, and AMD by an equally absurd margin in the other GNU radio results.

Same "GNU Radio" compiled binary on the respective platforms, huge swings in performance depending on what that binary was doing.

There were a couple other similar examples, where performance for the same program swung wildly depending on the exact task.

[minimaul]

That's not necessarily unexpected and still follows most of what I've said - if one particular algorithm is hand-optimised and one isn't, you will see wild swings - especially if one has been hand-vectorised and one is failing to auto-vectorise during compilation.