Skip to content
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

Merged
merged 1 commit into from
Oct 29, 2021

Conversation

aviatesk
Copy link
Member

Excited to tag the "embrassing-bugfix" label for the first time..

I will make a simple test case.

@nanosoldier runbenchmarks("union" || "array", vs="@2e388e3731fcdd8d1db4c1aed5c6a39df3ef7153")

@aviatesk aviatesk added embarrassing-bugfix Whoops! compiler:optimizer Optimization passes (mostly in base/compiler/ssair/) labels Oct 29, 2021
@KristofferC
Copy link
Member

I guess this should also be backported to 1.7?

@aviatesk
Copy link
Member Author

Ah, yes, we should.

@vchuravy
Copy link
Member

@nanosoldier runbenchmarks("union" || "array", vs="@2e388e3731fcdd8d1db4c1aed5c6a39df3ef7153")

@nanosoldier
Copy link
Collaborator

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here.

@nanosoldier
Copy link
Collaborator

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here.

@aviatesk
Copy link
Member Author

It seems like the allocation regression has gone (I also confirmed on my machine). Should be good to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler:optimizer Optimization passes (mostly in base/compiler/ssair/) embarrassing-bugfix Whoops!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants