## re: AES intrinsics and aarch64 here's a rabbit hole. - [commit adding aes support for aarch64 in go](https://cs.opensource.google/go/go/+/73e0c302b2bcf26c009f682c2c11ef3567854d46) 2018 - [specifically this bit](https://cs.opensource.google/go/go/+/master:src/runtime/asm_arm64.s;l=539-543) - [fix for perf regression in JDK with aes intrinsics vis a vis x86 and aarch64](https://github.com/openjdk/jdk11u-dev/pull/410) - [issue discussing the regression - graviton](https://github.com/aws/aws-graviton-getting-started/issues/110) - [Neoverse N1 Software Optimization Guide](https://documentation-service.arm.com/static/5f05e93dcafe527e86f61acd?token=) (referenced in thread above). From my reading, I'm not sure the [[golang]] implementation is optimal, but it does appear the go runtime takes advantage of AES instructions, at least graviton2 and up.