-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
[mlir][IR] Change MutableArrayRange
to enumerate OpOperand &
#66622
[mlir][IR] Change MutableArrayRange
to enumerate OpOperand &
#66622
Conversation
In line with llvm#66515, change `MutableArrayRange::begin`/`end` to enumerate `OpOperand &` instead of `Value`. Also a remove `ForOp::getIterOpOperands`/`setIterArg`, which are now redundant. Note: `MutableOperandRange` cannot be made a derived class of `indexed_accessor_range_base` (like `OperandRange`), because `MutableOperandRange::assign` can change the number of operands in the range.
@llvm/pr-subscribers-mlir-core @llvm/pr-subscribers-mlir-scf ChangesIn line with #66515, change Note:
|
…m#66622) In line with llvm#66515, change `MutableArrayRange::begin`/`end` to enumerate `OpOperand &` instead of `Value`. Also remove `ForOp::getIterOpOperands`/`setIterArg`, which are now redundant. Note: `MutableOperandRange` cannot be made a derived class of `indexed_accessor_range_base` (like `OperandRange`), because `MutableOperandRange::assign` can change the number of operands in the range.
In line with #66515, change
MutableArrayRange::begin
/end
to enumerateOpOperand &
instead ofValue
. Also removeForOp::getIterOpOperands
/setIterArg
, which are now redundant.Note:
MutableOperandRange
cannot be made a derived class ofindexed_accessor_range_base
(likeOperandRange
), becauseMutableOperandRange::assign
can change the number of operands in the range.