In other benchmarks like geekbench, which are not benchmarking golang's libs, the M1 is massively stronger than Intel on e.g. AES-XTS.
https://www.extremetech.com/computing/317304-benchmark-resul...
So hopefully the M1 gets the same hand-optimizing effort that x86 historically got.
Go libs just need to be tweaked to use the correct chip to do the work.
Looks like they did do AES-XTS on the main die because it is required for encrypted storage.
> A top level takeaway from this data is that for things that rely on pure Go the M1 machine is, in general, a good bit faster than the Intel machine. For code that relies on highly optimized assembly, like a good chunk of the crypto/ code, the Intel machine wins (although I wouldn’t be surprised to see significant gains for the M1 as arm64 assembly implementations get more attention and are further polished).
Basically Go lacks lots of optimized assembly code for ARM64.
https://github.com/golang/go/blob/master/src/crypto/aes/asm_...