-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[WIP][stdlib] Finalize Hasher ABI #19685
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
Conversation
@swift-ci smoke benchmark |
The optimizer dislikes nested switch statements; flatten them out to simplify optimization and to hopefully speed things up a little.
Build comment file:Performance: -O
Code size: -O
Performance: -Osize
Code size: -Osize
Performance: -Onone
Code size: Swift libraries
How to read the dataThe tables contain differences in performance which are larger than 8% and differences in code size which are larger than 1%.If you see any unexpected regressions, you should consider fixing the regressions before you merge the PR. Noise: Sometimes the performance results (not code size!) contain false alarms. Unexpected regressions which are marked with '(?)' are probably noise. If you see regressions which you cannot explain you can try to run the benchmarks again. If regressions still show up, please consult with the performance team (@eeckstein). Hardware Overview
|
Results seem to be roughly in line with #18953, or even worse. Making the tail inlinable may not actually be an optimization. |
Next up, let's start using |
@swift-ci please smoke benchmark |
I spawned #19688 to test the |
Build comment file:Performance: -O
Code size: -O
Performance: -Osize
Code size: -Osize
Performance: -Onone
Code size: Swift libraries
How to read the dataThe tables contain differences in performance which are larger than 8% and differences in code size which are larger than 1%.If you see any unexpected regressions, you should consider fixing the regressions before you merge the PR. Noise: Sometimes the performance results (not code size!) contain false alarms. Unexpected regressions which are marked with '(?)' are probably noise. If you see regressions which you cannot explain you can try to run the benchmarks again. If regressions still show up, please consult with the performance team (@eeckstein). Hardware Overview
|
This PR will finalize the ABI of Hasher. It looks like we may need to keep Hasher fixed-layout, with some extra padding to allow for potential future changes.
However, we should experiment with a few more ideas before committing to do that.
First, let's try making the tail buffer inlinable.