This PR fixes several build issues using GCC and shared libraries that have been introduced by the most recent BufferPlacement updates.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Added an additional comment and change to code to use the implicit OperandRange conversion operator.
Comment Actions
Accepted, but after
OperandRange range = successorOperand;
Value sourceValue = range[0];
is rewritten.
mlir/lib/Transforms/BufferPlacement.cpp | ||
---|---|---|
341 | i bet this can be written simpler without converting to OperandRange. |
mlir/lib/Transforms/BufferPlacement.cpp | ||
---|---|---|
341 | As discussed offline, a possible alternative would be OperandRange{successorOperand}.begin. |
Comment Actions
Refactored access to getSuccessorOperands to distinguish between read-only and write-enabled accesses.
i bet this can be written simpler without converting to OperandRange.