Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
Split out from #23929. No reason to have lots of different zero-valued readonly symbols when we can re-use runtime.zeroVal.
The text was updated successfully, but these errors were encountered:
Is this for performance, or to reduce binary size? Or perhaps both?
Sorry, something went wrong.
Performance: lower cache impact of reading zero values.
Binary size: fewer symbols.
Toolspeed: less to link.
I’d expect very minor improvements on all three.
Change https://golang.org/cl/186477 mentions this issue: cmd/compile: optimize comparisons with zero values
cmd/compile: optimize comparisons with zero values
This was my first serious foray into the front-end. I wanted to take this opportunity and thank @martisch for guiding me on this, and his patience for bearing with my questions while stumbling around the front-end code. Thanks Martin !
Successfully merging a pull request may close this issue.