-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
[WIP] Switch StableHasher from SipHash to HighwayHash #84229
Conversation
This changes the hash in the legacy symbol mangling format - if this is undesired, we could use SipHash just for symbol mangling.
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 821161a with merge 0f5be41e96dee6e68543cb90326bdea0bc24f3a4... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Try build successful - checks-actions |
Queued 0f5be41e96dee6e68543cb90326bdea0bc24f3a4 with parent 60158f4, future comparison URL. |
Finished benchmarking try commit (0f5be41e96dee6e68543cb90326bdea0bc24f3a4): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
merge conflicts + build failures |
This was a performance loss on all benchmarks. |
This changes the hash in the legacy symbol mangling format - if this is
undesired, we could use SipHash just for symbol mangling.
r? @ghost