-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
[MachineInstr] add insert method for variadic instructions #67699
Merged
nickdesaulniers
merged 11 commits into
llvm:main
from
nickdesaulniers:MachineInstrInsert
Oct 30, 2023
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
ff094aa
[MachineInstr] add insert method for variadic instructions
nickdesaulniers eb410ae
fix tied operands insertion
nickdesaulniers e5ed345
add tied ops test
nickdesaulniers 92d53e9
test bad inputs
nickdesaulniers 6ec4178
s/DenseMap/SmallDenseMap/
nickdesaulniers 381dd4c
remove const
nickdesaulniers 4a862dd
remove support for null iterator
nickdesaulniers 69b94e3
move assert earlier
nickdesaulniers 0d7d924
git clang-format HEAD~8
nickdesaulniers 8449626
make sure registerclass is allocatable before changing operands
nickdesaulniers 6ba0e06
rename parameter
nickdesaulniers File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains 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 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 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.
Maybe do this in reverse order so we waste less cycles on the
moveOperands()
call withinMachineInstr::removeOperand()
. On that note I wonder ifmoveOperands()
would work here as well instead of theremoveOperand
/addOperand
forMovingOps
here?Admittedly it looks like
moveOperands()
doesn't really adjust theTiedTo
markers so that's why it wouldn't work here?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.
The issue there is we would miss the calls to
MachineFunction::allocateOperandArray
fromMachineInstr::addOperand
. Since splice grows the operand list, we need to realloc the storage for the operands.MachineInstr::moveOperands
justmemmove
s operands around which is not safe to do when the backing store hasn't been grown.That's also an issue, though I'm manually handling tied operands.
I don't think there are any cycles to be saved? Perhaps if splice is being used to append operands on the end? Usually you splice operands into the middle, so you need to memmove the elements occurring after the insertion point multiple times.
Notice in this loop that the induction variable
I
is not being used as an index; we're removingOpIdx
repeatedly as this is slicing off the elements past the insertion point.Later, we need to re-add the operands back in the correct order (though it's not hard to reverse the loop below).
Did I perhaps miss something though?
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.
make sense. I haven't looked at the code as deeply as you have; just wanted to ask the questions to make sure :)