-
Notifications
You must be signed in to change notification settings - Fork 14.4k
InlineFunction: Split inlining into predicate and apply functions #134213
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
arsenm
wants to merge
1
commit into
main
Choose a base branch
from
users/arsenm/inline-function/split-legality-predicate-and-impl
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -263,6 +263,9 @@ class InlineFunctionInfo { | |
/// `InlinedCalls` above is used. | ||
SmallVector<CallBase *, 8> InlinedCallSites; | ||
|
||
Value *ConvergenceControlToken = nullptr; | ||
Instruction *CallSiteEHPad = nullptr; | ||
|
||
/// Update profile for callee as well as cloned version. We need to do this | ||
/// for regular inlining, but not for inlining from sample profile loader. | ||
bool UpdateProfile; | ||
|
@@ -271,9 +274,34 @@ class InlineFunctionInfo { | |
StaticAllocas.clear(); | ||
InlinedCalls.clear(); | ||
InlinedCallSites.clear(); | ||
ConvergenceControlToken = nullptr; | ||
CallSiteEHPad = nullptr; | ||
} | ||
}; | ||
|
||
/// Check if it is legal to perform inlining of the function called by \p CB | ||
/// into the caller at this particular use, and sets fields in \p IFI. | ||
/// | ||
/// This does not consider whether it is possible for the function callee itself | ||
/// to be inlined; for that see isInlineViable. | ||
InlineResult CanInlineCallSite(const CallBase &CB, InlineFunctionInfo &IFI); | ||
|
||
/// This should generally not be used, use InlineFunction instead. | ||
/// | ||
/// Perform mechanical inlining of \p CB into the caller. | ||
/// | ||
/// This does not perform any legality or profitability checks for the | ||
/// inlining. This assumes that CanInlineCallSite was already called, populated | ||
/// \p IFI, and returned InlineResult::success. | ||
/// | ||
/// Also assumes that isInlineViable returned InlineResult::success for the | ||
/// called function. | ||
Comment on lines
+297
to
+298
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. Perhaps worth an assert then? |
||
void InlineFunctionImpl(CallBase &CB, InlineFunctionInfo &IFI, | ||
bool MergeAttributes = false, | ||
AAResults *CalleeAAR = nullptr, | ||
bool InsertLifetime = true, | ||
Function *ForwardVarArgsTo = nullptr); | ||
|
||
/// This function inlines the called function into the basic | ||
/// block of the caller. This returns false if it is not possible to inline | ||
/// this call. The program is still in a well defined state if this occurs | ||
|
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
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.
Yeah, I'd be curious to know more about why someone would call
isInlineViable
vsCanInlineCallsite
? The names alone sound like synonyms to me...Is one doing checks the other should be doing, or vice versa? If so, perhaps they should just be one function...
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.
They should not be one function, and I think I think the split makes sense, but the names need work. A wrapper function which calls the two would be useful, but they should be available as the split parts.
isInlineViable is a restriction on ever inlining the function based on the callee's properties. As in, the inliner cannot physically inline the function. You can pre-filter handling functions which will never be inlined.
CanInlineCallsite is for context sensitive restrictions at the specific callsite. It's a property of the caller, more than the callee