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

Put back @inline on unsafe_getindex #51160

Merged
merged 1 commit into from
Sep 5, 2023
Merged

Conversation

LilithHafner
Copy link
Member

Fixup for #50467

@nanosoldier runbenchmarks("array", vs="@fb7613635cab77cf269790335e8121f513c9ea96")

@nanosoldier
Copy link
Collaborator

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

@LilithHafner
Copy link
Member Author

All regressions look like noise to me. I failed to reproduce the largest regression (1.49x) locally. The comparison build was the parent of #50467, so I think this fix catches everything.

@LilithHafner LilithHafner requested a review from vtjnash September 2, 2023 18:31
@LilithHafner
Copy link
Member Author

This fixes a regression and all tests pass so I'm going to go ahead and merge it.

@LilithHafner LilithHafner merged commit 00ca93c into master Sep 5, 2023
@LilithHafner LilithHafner deleted the lh/50467-perf-fixup branch September 5, 2023 14:05
@vtjnash
Copy link
Member

vtjnash commented Sep 5, 2023

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Must go faster
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants