-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
optimizer: fix #42840, the performance regression introduced by #42766 #42841
Conversation
I guess this should also be backported to 1.7? |
Ah, yes, we should. |
@nanosoldier |
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. |
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. |
It seems like the allocation regression has gone (I also confirmed on my machine). Should be good to go. |
Excited to tag the "embrassing-bugfix" label for the first time..
I will make a simple test case.
@nanosoldier
runbenchmarks("union" || "array", vs="@2e388e3731fcdd8d1db4c1aed5c6a39df3ef7153")