Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Analysis] Use BitVector::test in areInlineCompatible (NFC) #98776

Merged
merged 1 commit into from
Jul 14, 2024
Merged

[Analysis] Use BitVector::test in areInlineCompatible (NFC) #98776

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions llvm/include/llvm/Analysis/TargetLibraryInfo.h
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -327,11 +327,9 @@ class TargetLibraryInfo {
bool AllowCallerSuperset) const {
if (!AllowCallerSuperset)
return OverrideAsUnavailable == CalleeTLI.OverrideAsUnavailable;
BitVector B = OverrideAsUnavailable;
B |= CalleeTLI.OverrideAsUnavailable;
// We can inline if the union of the caller and callee's nobuiltin
// attributes is no stricter than the caller's nobuiltin attributes.
return B == OverrideAsUnavailable;
// We can inline if the callee's nobuiltin attributes are no stricter than
// the caller's.
return !CalleeTLI.OverrideAsUnavailable.test(OverrideAsUnavailable);
}

/// Return true if the function type FTy is valid for the library function
Expand Down
Loading