That's a fantastic score and, from some GB6 estimates by Arm, X925 SoCs will be notably behind. I won't know much beyond you or others, though.
https://browser.geekbench.com/v6/cpu/compare/7714502?baseline=7720191 (vs the highest A18 score so far)
If we want to isolate without SME (
which is another discussion: how frequently is it used in Android in these workloads?), a GB6.2 run on them both would be ideal.
// looking at 1T
The best I can note is that the Pts / GHz is much closer to what Qualcomm initially claimed (3227 / 4.2 GHz = ~768 Pts / GHz in for the X Elite under Linux; this score is 3216 / 4.3 GHz = ~748 Pts / GHz; X Elite on Windows is closer to ~711 Pts / GHz) from Oryon. I assume there's something unique in the Oryon uArch that lets it run noticeably better under Linux systems (e.g., some of the same branch prediction stuff we saw with AMD?).
Maybe Arm X925 smartphones will be only ones below 4 GHz next year. A18 / M4 is likely to keep the overall Pts / GHz "crown" here, though the X Elite as the clocked +6% higher.
In 1-2 subtests, though, Oryon has a slightly
higher Pts / GHz (!): see PDF renderer & HDR.
A18: 3261 pts @ 4.04 GHz → 807.2 Pts / GHz
Oryon: 3644 pts @ 4.3 GHz → 847.4 Pts / GHz (+5%)
HDR is 1% advantage for Oryon, as well. Notably, neither test uses SME.
// looking at nT
This is more a PL1 / burst power limit test, but Oryon is notably faster over the A18 (though it's +20% with ~33% more cores).
//
That is possible. IIRC, the OnePlus & Samsung schemes were to throttle non-benchmark apps; technically, the benchmarks showed the SoCs at their best: they just refused to let users
actually use that power in anything else. So benchmarks were ran faster than real apps (thus cheating), but by slowing down real apps, versus boosting benchmarks.
Tactic 1: boost benchmarks, normal perf in real apps
Tactic 2: normal perf in benchmarks, throttle real apps
I believe it was Tactic 2.