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.
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
[ObjectFifo][NFC] Refactor DmaUtils + SplitLogicalObjectFifoForReuse #759
[ObjectFifo][NFC] Refactor DmaUtils + SplitLogicalObjectFifoForReuse #759
Changes from 1 commit
d63ff63
07df743
3c94df7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Relaying here the review comment : #755 (comment) (@jtuyls )
Two reasons :-
SmallVector<arg1, arg2>
used to be mandatory but stopped being so - I came across this relaxed constraint in one of the upstream contribution's review comments.createNewLogicalObjectFifo
declaration complains because :-a.
SmallVector<arg1>
!=SmallVector<arg1, 4>
b.
SmallVector<arg1, 4>
!=SmallVector<arg1, 6>
Therefore the only way to circumvent point 2z, that I knew of, was to remove this which aligned well with point 1.
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.
I think it's still useful to specify the number of inlined elements in the vector as we know it will usually be less than 4 and not much more:
SmallVector<OpFoldResult, 4>
.createNewLogicalObjectFifo
then has to accept aSmallVectorImpl
instead of aSmallVector
to avoid the issue in 2).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.
Sure, I've addressed it in the latest push. Please take a look.