Open aadomnicai opened 2 weeks ago
Similar Issues
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)
It looks like x/sys/cpu parses registers https://go.googlesource.com/sys/+/76700875dfcc135287c18189252576117307b695/cpu/cpu_arm64.go#73 While the go repo's internal/cpu just assumes support https://go.googlesource.com/go/+/e8ee1dc4f9e2632ba1018610d1a1187743ae397f/src/internal/cpu/cpu_arm64_darwin.go#20
Thanks for pointing this out. Any insight on why this has not been merged so far?
Thanks for pointing this out.
Any insight on why this has not been merged so far?
I need to make the fixes requested by the reviewers, then it needs to be reviewed again.
This is mostly a dupe of https://github.com/golang/go/issues/43046
Your responses to the remaining two issues make sense to me, and it seems that it could be merged as it is. Any idea of why the reviewer did not provide feedback?
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Run a simple test to check whether hardware AES is used on my machine. The following is simply run with
go test -tags ""
What did you expect to see?
I would have expected
Hardware AES is used: true
since AES instructions are supported. Ingo/src/internal/cpu/cpu_arm64_darwin.go
, the variablecpu.ARM64.HasAES
should be set totrue
, and I cannot understand why that is not the case since the build conditions//go:build arm64 && darwin && !ios
should be satisfied?What did you see instead?
I get
Hardware AES is used: false
instead.