Faster integer hashing (fixes #37800 UB)#38031
Merged
Conversation
Contributor
|
With this PR you have |
b5ff5f3 to
ebb267a
Compare
Member
Author
|
Ah, you're right. Good catch. I completely botched that and forgot to use |
Member
Author
|
triage concluded to simplify this (disable the breaking tests), and otherwise to proceed |
In LLVM (inherited from C), fptosi has undefined behavior if the result does not fit the integer size after rounding down. But by using the same strategy as generic hashing of Real values, we actually can end up with a sitatuion that is faster for the CPU to deal with and avoids the UB. Refs #6624 (3696968) Fixes #37800
ebb267a to
a38c088
Compare
Member
|
What is holding this up? IIRC Triage ok'ed this, so can we just merge it? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In LLVM (inherited from C), fptosi has undefined behavior if the result
does not fit the integer size after rounding down. But by using the same
strategy as generic hashing of Real values, we actually can end up with
a situation that is not much slower for the CPU to deal with and avoids
the UB.
Refs #6624 (3696968)
Fixes #37800
Benchmarks:
Aside: note that integers-as-floating-point aren't affected as much:
@StefanKarpinski I picked these factors mostly at random. So if you have better ideas for the specific hashing function itself, I'll update to that. This is showing the general idea and testing performance of it.