-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[libc] Remove UB specializations of type traits for BigInt
#84035
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
Merged
gchatelet
merged 4 commits into
llvm:main
from
gchatelet:use_return_type_sfinae_for_bit_utils
Mar 7, 2024
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
528b7ce
[libc] Remove UB specializations of type_traits
gchatelet ccabea0
Fix bug on has_single_bit
gchatelet 71a1599
implement faster count_ones count_zeros, add documentation
gchatelet 48b0bc8
Remove non standard bit functions specializations, add documentation …
gchatelet File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a side question: Is there a simple way to make these template functions be like:
Especially if this pattern can be applied to many functions easily somehow.
Last time I experimented with
DoubleDouble
andDyadicFloat<128>
and it did provide measurable performance improvements.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All our functions are
inline
. This means that the compiler can change how the value is passed to the function. That is, we don't care about passing by value or ref.The only thing we need to make sure is that the type is
[[trivial_abi]]
(blog article), otherwise the compiler is forced to pass by ref to be able to call the destructor when there is one. This is true even if the signature of the function passes the argument by value. So technically we'd need to annotateBigInt
andDoubleDouble
with[[clang::trivial_abi]]
(or its GCC equivalent). We can alsostatic_assert<cpp::is_trivial_v<T>>
forDoubleDouble
andDyadicFloat<128>
.