-
Notifications
You must be signed in to change notification settings - Fork 14.4k
[Transforms] Introduce BuildBuiltins.h atomic helpers #134455
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
Open
Meinersbur
wants to merge
3
commits into
main
Choose a base branch
from
users/meinersbur/llvm_buildbuiltins
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -80,6 +80,48 @@ class ValueMatchesPoly { | |
M Matcher; | ||
}; | ||
|
||
template <typename RefT> class StoreResultMatcher { | ||
class Impl : public testing::MatcherInterface< | ||
const llvm::detail::ExpectedHolder<RefT> &> { | ||
public: | ||
explicit Impl(RefT &Ref) : Ref(Ref) {} | ||
|
||
bool | ||
MatchAndExplain(const llvm::detail::ExpectedHolder<RefT> &Holder, | ||
testing::MatchResultListener *listener) const override { | ||
// If failed to get a value, fail the ASSERT/EXPECT and do not store any | ||
// value | ||
if (!Holder.Success()) | ||
return false; | ||
|
||
// Succeeded with a value, remember it | ||
Ref = *Holder.Exp; | ||
|
||
return true; | ||
} | ||
|
||
void DescribeTo(std::ostream *OS) const override { *OS << "succeeded"; } | ||
|
||
void DescribeNegationTo(std::ostream *OS) const override { | ||
*OS << "failed"; | ||
} | ||
|
||
private: | ||
RefT &Ref; | ||
}; | ||
|
||
public: | ||
explicit StoreResultMatcher(RefT &Ref) : Ref(Ref) {} | ||
|
||
template <typename T> | ||
operator testing::Matcher<const llvm::detail::ExpectedHolder<T> &>() const { | ||
return MakeMatcher(new Impl(Ref)); | ||
} | ||
|
||
private: | ||
RefT &Ref; | ||
}; | ||
|
||
template <typename InfoT> | ||
class ErrorMatchesMono : public testing::MatcherInterface<const ErrorHolder &> { | ||
public: | ||
|
@@ -222,6 +264,13 @@ detail::ValueMatchesPoly<M> HasValue(M Matcher) { | |
return detail::ValueMatchesPoly<M>(Matcher); | ||
} | ||
|
||
/// Matches on Expected<T> values that succeed, but also stores its value into a | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe this addition to the testing support should go in a different PR? |
||
/// variable. | ||
template <typename RefT> | ||
detail::StoreResultMatcher<RefT> StoreResult(RefT &Ref) { | ||
return detail::StoreResultMatcher<RefT>(Ref); | ||
} | ||
|
||
} // namespace llvm | ||
|
||
#endif |
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.
Is the choice to let
__atomic_load_N
return a sized integer, while__atomic_load
return void based on maintaining proximity with GCC's definitions of these builtins? Or is there any other reason which I am missing?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.
This is the GCC-defined ABI, see https://gcc.gnu.org/wiki/Atomic/GCCMM/LIbrary#GCC_intrinsics for reference.
__atomic_load_N
returns the load value, possible due to having a known size that fits into a register (or pre-allocated stack slot, depending on calling convention).__atomic_load
reads a dynamic number of bytes and hence cannot be pre-allocated/passed by register.