[mlir][linalg][bufferize][NFC] Conflict detection funcs take OpOperand and OpResult
authorMatthias Springer <springerm@google.com>
Wed, 13 Oct 2021 00:16:29 +0000 (09:16 +0900)
committerMatthias Springer <springerm@google.com>
Wed, 13 Oct 2021 00:17:31 +0000 (09:17 +0900)
commitfd3162042022767a9cc8a03e6ccd5fa257fda5d7
treed02c3aa64f9af3dd777652c319dfe6c3d1723824
parent02410df530fbef5256711ec2220c4c34468c894c
[mlir][linalg][bufferize][NFC] Conflict detection funcs take OpOperand and OpResult

By doing so, it is not necessary to get the OpOperand a second time via
getAliasingOpOperand. Also, code slightly more readable because we do
not have to deal with Optional<> return value.

Differential Revision: https://reviews.llvm.org/D110918
mlir/include/mlir/Dialect/Linalg/Transforms/ComprehensiveBufferize.h
mlir/lib/Dialect/Linalg/Transforms/ComprehensiveBufferize.cpp