-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/compile: add reassociate pass to find better optimization opportunities within commutative expressions #60015
New issue
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? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…ions Currently the compiler groups expressions with commutative operations such as a + b + c + d as so: (a + (b + (c + d))) which is suboptimal for CPU instruction pipelining. This pass balances commutative expressions as shown above to (a + b) + (c + d) to optimally pipeline them. It also attempts to reassociate constants to as far right of the commutative expression as possible for better constant folding opportunities. Below is a benchmark from crypto/md5 on an MacBook Pro M2: trunk reassociate Hash1K-8 433.7Mi ± 0% 499.4Mi ± 4% +15.17% (p=0.000 n=10) Hash8K-8 454.3Mi ± 1% 524.9Mi ± 1% +15.53% (p=0.000 n=10) .... geomean 284.4Mi 327.5Mi +15.15% Other CPU architectures tried showed very little change (+/-1%) on this particular benchmark but tight mathematical code stands to gain greatly from this optimization Fixes golang#49331
This PR (HEAD: c7ac24f) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/go/+/493115 to see it. Tip: You can toggle comments from me using the |
Message from Gopher Robot: Patch Set 1: Congratulations on opening your first change. Thank you for your contribution! Next steps: Most changes in the Go project go through a few rounds of revision. This can be During May-July and Nov-Jan the Go project is in a code freeze, during which Please don’t reply on this GitHub thread. Visit golang.org/cl/493115. |
This PR (HEAD: 5ad3fc9) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/go/+/493115 to see it. Tip: You can toggle comments from me using the |
Message from [email protected]: Patch Set 3: (1 comment) Please don’t reply on this GitHub thread. Visit golang.org/cl/493115. |
Message from Keith Randall: Patch Set 4: (12 comments) Please don’t reply on this GitHub thread. Visit golang.org/cl/493115. |
This PR (HEAD: 1c2d148) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/go/+/493115 to see it. Tip: You can toggle comments from me using the |
This PR (HEAD: 4846c63) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/go/+/493115 to see it. Tip: You can toggle comments from me using the |
Message from Ryan Berger: Patch Set 5: (12 comments) Please don’t reply on this GitHub thread. Visit golang.org/cl/493115. |
Message from Keith Randall: Patch Set 6: (4 comments) Please don’t reply on this GitHub thread. Visit golang.org/cl/493115. |
Message from Ryan Berger: Patch Set 6: (3 comments) Please don’t reply on this GitHub thread. Visit golang.org/cl/493115. |
Message from Keith Randall: Patch Set 6: Hold+1 Please don’t reply on this GitHub thread. Visit golang.org/cl/493115. |
[WIP] - separating out ILP work and reassociation work
reassociation should help (a + (b + (a + (b + (a + (b + a))))) get optimized to (4a + 4b),
ilp should help (a + (b + (c + d))) turn into (a + b) + (c + d)