MLIR 22.0.0git
OneShotAnalysis.cpp File Reference

Go to the source code of this file.

Macros

#define DEBUG_TYPE   "one-shot-analysis"

Functions

static bool isaTensor (Type t)
static void setInPlaceOpOperand (OpOperand &opOperand, bool inPlace)
 Mark whether OpOperand will be bufferized inplace.
static bool isInplaceMemoryWrite (OpOperand &opOperand, const OneShotAnalysisState &state)
 Return true if opOperand has been decided to bufferize in-place.
static bool happensBefore (Operation *a, Operation *b, const DominanceInfo &domInfo)
 Return true if a happens before b, i.e., a or one of its ancestors properly dominates b and b is not inside a.
static bool canUseOpDominanceDueToRegions (OpOperand *uRead, OpOperand *uWrite, const SetVector< Value > &definitions, AnalysisState &state)
 Return true if op dominance can be used to rule out a read-after-write conflicts based on the ordering of ops.
static bool canUseOpDominanceDueToBlocks (OpOperand *uRead, OpOperand *uWrite, const SetVector< Value > &definitions, AnalysisState &state)
 Return true if op dominance can be used to rule out a read-after-write conflicts based on the ordering of ops.
static bool canUseOpDominance (OpOperand *uRead, OpOperand *uWrite, const SetVector< Value > &definitions, AnalysisState &state)
static void annotateConflict (OpOperand *uRead, OpOperand *uConflictingWrite, Value definition)
 Annotate IR with details about the detected RaW conflict.
static bool hasEquivalentValueInReverseUseDefChain (AnalysisState &state, OpOperand *start, Value other)
 Return 'true' if a tensor that is equivalent to other can be found in the reverse use-def chain of start.
static bool matchesInsertDestination (const AnalysisState &state, OpOperand *opOperand, SubsetInsertionOpInterface subsetOp)
 Return "true" if the given operand's value is originating from a subset that is equivalent to the subset that subsetOp inserts into.
static bool areNonConflictingSubsets (OpOperand *uRead, OpOperand *uConflictingWrite, const AnalysisState &state)
 Return "true" if the given "read" and potentially conflicting "write" are not conflicting due to their subset relationship.
static bool hasReadAfterWriteInterference (const DenseSet< OpOperand * > &usesRead, const DenseSet< OpOperand * > &usesWrite, const DominanceInfo &domInfo, OneShotAnalysisState &state)
 Given sets of uses and writes, return true if there is a RaW conflict under the assumption that all given reads/writes alias the same buffer and that all given writes bufferize inplace.
static void getAliasingInplaceWrites (DenseSet< OpOperand * > &res, Value root, const OneShotAnalysisState &state)
static void getAliasingReads (DenseSet< OpOperand * > &res, Value root, const OneShotAnalysisState &state)
static bool wouldCreateReadAfterWriteInterference (OpOperand &operand, const DominanceInfo &domInfo, OneShotAnalysisState &state, bool checkConsistencyOnly=false)
 Return true if bufferizing operand inplace would create a conflict.
static void annotateNonWritableTensor (Value value)
 Annotate IR with details about the detected non-writability conflict.
static bool wouldCreateWriteToNonWritableBuffer (OpOperand &operand, OneShotAnalysisState &state, bool checkConsistencyOnly=false)
 Return true if bufferizing operand inplace would create a write to a non-writable buffer.
static LogicalResult bufferizableInPlaceAnalysisImpl (OpOperand &operand, OneShotAnalysisState &state, const DominanceInfo &domInfo)
 Determine if operand can be bufferized in-place.
static void equivalenceAnalysis (SmallVector< Operation * > &ops, OneShotAnalysisState &state)
 Analyze equivalence of tied OpResult/OpOperand pairs of the given ops.
static void equivalenceAnalysis (Operation *op, OneShotAnalysisState &state)
 Analyze equivalence of tied OpResult/OpOperand pairs of all ops contained in op.
static SmallVector< Operation * > bottomUpFromTerminatorsHeuristic (Operation *op, const OneShotAnalysisState &state)
 "Bottom-up from terminators" heuristic.
static LogicalResult checkPreBufferizationAssumptions (Operation *op, const DominanceInfo &domInfo, OneShotAnalysisState &state)
 Perform various checks on the input IR to see if it contains IR constructs that are unsupported by One-Shot Bufferize.
static void annotateOpsWithBufferizationMarkers (Operation *op, const OneShotAnalysisState &state)
 Annotate the IR with the result of the analysis. For testing/debugging only.
static void annotateOpsWithAliasSets (Operation *op, const OneShotAnalysisState &state)

Variables

constexpr StringLiteral kInPlaceOperandsAttrName = "__inplace_operands_attr__"
 Attribute marker to specify op operands that bufferize in-place.
constexpr StringLiteral kOpResultAliasSetAttrName
constexpr StringLiteral kBbArgAliasSetAttrName = "__bbarg_alias_set_attr__"

Macro Definition Documentation

◆ DEBUG_TYPE

#define DEBUG_TYPE   "one-shot-analysis"

Definition at line 65 of file OneShotAnalysis.cpp.

Function Documentation

◆ annotateConflict()

void annotateConflict ( OpOperand * uRead,
OpOperand * uConflictingWrite,
Value definition )
static

Annotate IR with details about the detected RaW conflict.

Definition at line 431 of file OneShotAnalysis.cpp.

References b, mlir::Operation::getContext(), mlir::OpOperand::getOperandNumber(), mlir::detail::IROperandBase::getOwner(), and mlir::Operation::setAttr().

Referenced by hasReadAfterWriteInterference().

◆ annotateNonWritableTensor()

void annotateNonWritableTensor ( Value value)
static

Annotate IR with details about the detected non-writability conflict.

Definition at line 899 of file OneShotAnalysis.cpp.

References b, and mlir::Value::getContext().

Referenced by wouldCreateWriteToNonWritableBuffer().

◆ annotateOpsWithAliasSets()

◆ annotateOpsWithBufferizationMarkers()

void annotateOpsWithBufferizationMarkers ( Operation * op,
const OneShotAnalysisState & state )
static

Annotate the IR with the result of the analysis. For testing/debugging only.

Definition at line 1252 of file OneShotAnalysis.cpp.

References mlir::Operation::getOpOperands(), mlir::bufferization::OneShotAnalysisState::isInPlace(), setInPlaceOpOperand(), and mlir::Operation::walk().

Referenced by mlir::bufferization::analyzeOp().

◆ areNonConflictingSubsets()

bool areNonConflictingSubsets ( OpOperand * uRead,
OpOperand * uConflictingWrite,
const AnalysisState & state )
static

Return "true" if the given "read" and potentially conflicting "write" are not conflicting due to their subset relationship.

The comments in this function are expressed in terms of tensor.extract_slice/tensor.insert_slice pairs, but apply to any subset ops that implement the SubsetInsertionOpInterface.

Definition at line 508 of file OneShotAnalysis.cpp.

References mlir::IROperand< DerivedT, IRValueT >::get(), mlir::detail::IROperandBase::getOwner(), and matchesInsertDestination().

Referenced by hasReadAfterWriteInterference().

◆ bottomUpFromTerminatorsHeuristic()

SmallVector< Operation * > bottomUpFromTerminatorsHeuristic ( Operation * op,
const OneShotAnalysisState & state )
static

◆ bufferizableInPlaceAnalysisImpl()

◆ canUseOpDominance()

bool canUseOpDominance ( OpOperand * uRead,
OpOperand * uWrite,
const SetVector< Value > & definitions,
AnalysisState & state )
static

◆ canUseOpDominanceDueToBlocks()

bool canUseOpDominanceDueToBlocks ( OpOperand * uRead,
OpOperand * uWrite,
const SetVector< Value > & definitions,
AnalysisState & state )
static

Return true if op dominance can be used to rule out a read-after-write conflicts based on the ordering of ops.

Returns false if op dominance cannot be used to due block-based loops within a region.

Refer to the canUseOpDominanceDueToRegions documentation for details on how op domiance is used during RaW conflict detection.

On a high-level, there is a potential RaW in a program if there exists a possible program execution such that there is a sequence of DEF, followed by WRITE, followed by READ. Each additional DEF resets the sequence.

Op dominance cannot be used if there is a path from block(READ) to block(WRITE) and a path from block(WRITE) to block(READ). block(DEF) should not appear on that path.

Definition at line 401 of file OneShotAnalysis.cpp.

References mlir::Operation::getBlock(), mlir::detail::IROperandBase::getOwner(), mlir::Operation::getParentRegion(), and mlir::Block::isReachable().

Referenced by canUseOpDominance().

◆ canUseOpDominanceDueToRegions()

bool canUseOpDominanceDueToRegions ( OpOperand * uRead,
OpOperand * uWrite,
const SetVector< Value > & definitions,
AnalysisState & state )
static

Return true if op dominance can be used to rule out a read-after-write conflicts based on the ordering of ops.

Returns false if op dominance cannot be used to due region-based loops.

Generalized op dominance can often be used to rule out potential conflicts due to "read happens before write". E.g., the following IR is not a RaW conflict because the read happens before the write.

Example 1: %0 = ... : tensor<?xf32> // DEF "reading_op"(%0) : tensor<?xf32> // READ %1 = "writing_op"(%0) : tensor<?xf32> -> tensor<?xf32> // WRITE

This is no longer true inside loops (or repetitive regions). In such cases, there may not be a meaningful happensBefore relationship because ops could be executed multiple times. E.g.:

Example 2: %0 = ... : tensor<?xf32> // DEF scf.for ... { "reading_op"(%0) : tensor<?xf32> // READ %1 = "writing_op"(%0) : tensor<?xf32> -> tensor<?xf32> // WRITE ... }

In the above example, reading_op happens before writing_op according to op dominance. However, both ops may happen multiple times; in particular, the second execution of reading_op happens after the first execution of writing_op. This is problematic because the tensor %0 they operate on (i.e., the "definition") is defined outside of the loop.

On a high-level, there is a potential RaW in a program if there exists a possible program execution such that there is a sequence of DEF, followed by WRITE, followed by READ. Each additional DEF resets the sequence.

E.g.: No conflict: DEF, WRITE, DEF, READ Potential conflict: DEF, READ, WRITE, READ, WRITE

Example 1 has no conflict: DEF, READ, WRITE Example 2 has a potential conflict: DEF, (READ, WRITE)* Example 3: scf.for ... { %0 = ... : tensor<?xf32> "reading_op"(%0) : tensor<?xf32> %1 = "writing_op"(%0) : tensor<?xf32> -> tensor<?xf32> ... } This has no conflict: (DEF, READ, WRITE)*

Example 4: %0 = ... : tensor<?xf32> scf.for ... { scf.for ... { "reading_op"(%0) } %1 = "writing_op"(%0) } This has a potential conflict: DEF, ((READ)*, WRITE)*

Example 5: %0 = ... : tensor<?xf32> scf.for ... { %1 = "writing_op"(%0) } scf.for ... { "reading_op"(%0) } This has a potential conflict: DEF, WRITE*, READ*

The following rules are used to rule out RaW conflicts via ordering of ops:

  1. If the closest enclosing repetitive region of DEF is a proper ancestor of a repetitive region that enclosing both READ and WRITE, we cannot rule out RaW conflict due to the ordering of ops.
  2. Otherwise: There are no loops that interfere with our analysis; for analysis purposes, we can assume that there are no loops/repetitive regions. I.e., we can rule out a RaW conflict if READ happensBefore WRITE or WRITE happensBefore DEF. (Checked in hasReadAfterWriteInterference.)

Definition at line 355 of file OneShotAnalysis.cpp.

References mlir::detail::IROperandBase::getOwner(), mlir::Region::getParentOp(), mlir::Operation::isAncestor(), and options.

Referenced by canUseOpDominance().

◆ checkPreBufferizationAssumptions()

◆ equivalenceAnalysis() [1/2]

void equivalenceAnalysis ( Operation * op,
OneShotAnalysisState & state )
static

Analyze equivalence of tied OpResult/OpOperand pairs of all ops contained in op.

Definition at line 1056 of file OneShotAnalysis.cpp.

References equivalenceAnalysis(), mlir::Operation::getResultTypes(), isaTensor(), mlir::PostOrder, and mlir::Operation::walk().

◆ equivalenceAnalysis() [2/2]

◆ getAliasingInplaceWrites()

◆ getAliasingReads()

void getAliasingReads ( DenseSet< OpOperand * > & res,
Value root,
const OneShotAnalysisState & state )
static

◆ happensBefore()

bool happensBefore ( Operation * a,
Operation * b,
const DominanceInfo & domInfo )
static

Return true if a happens before b, i.e., a or one of its ancestors properly dominates b and b is not inside a.

Definition at line 267 of file OneShotAnalysis.cpp.

References b, mlir::Operation::getParentOp(), mlir::Operation::isProperAncestor(), and mlir::DominanceInfo::properlyDominates().

Referenced by hasReadAfterWriteInterference().

◆ hasEquivalentValueInReverseUseDefChain()

bool hasEquivalentValueInReverseUseDefChain ( AnalysisState & state,
OpOperand * start,
Value other )
static

Return 'true' if a tensor that is equivalent to other can be found in the reverse use-def chain of start.

Note: If an OpOperand bufferizes out of place along that use-def chain, the two tensors may not materialize as equivalent buffers (but separate allocations).

Note: This function also requires that the two tensors have equivalent indexing. I.e., the tensor types do not change along the use-def chain, apart from static <-> dynamic dim casts.

Definition at line 470 of file OneShotAnalysis.cpp.

References mlir::config.

Referenced by hasReadAfterWriteInterference().

◆ hasReadAfterWriteInterference()

bool hasReadAfterWriteInterference ( const DenseSet< OpOperand * > & usesRead,
const DenseSet< OpOperand * > & usesWrite,
const DominanceInfo & domInfo,
OneShotAnalysisState & state )
static

Given sets of uses and writes, return true if there is a RaW conflict under the assumption that all given reads/writes alias the same buffer and that all given writes bufferize inplace.

A conflict is: According to SSA use-def chains, a read R is supposed to read the result of a definition W1. But because of bufferization decisions, R actually reads another definition W2.

Definition at line 590 of file OneShotAnalysis.cpp.

References annotateConflict(), areNonConflictingSubsets(), canUseOpDominance(), mlir::Block::findAncestorOpInBlock(), mlir::bufferization::OneShotAnalysisState::findDefinitionsCached(), mlir::bufferization::OneShotAnalysisState::getOptions(), happensBefore(), hasEquivalentValueInReverseUseDefChain(), and options.

Referenced by wouldCreateReadAfterWriteInterference().

◆ isaTensor()

◆ isInplaceMemoryWrite()

bool isInplaceMemoryWrite ( OpOperand & opOperand,
const OneShotAnalysisState & state )
static

Return true if opOperand has been decided to bufferize in-place.

Definition at line 256 of file OneShotAnalysis.cpp.

References mlir::bufferization::OneShotAnalysisState::isInPlace().

Referenced by getAliasingInplaceWrites().

◆ matchesInsertDestination()

bool matchesInsertDestination ( const AnalysisState & state,
OpOperand * opOperand,
SubsetInsertionOpInterface subsetOp )
static

Return "true" if the given operand's value is originating from a subset that is equivalent to the subset that subsetOp inserts into.

Definition at line 485 of file OneShotAnalysis.cpp.

Referenced by areNonConflictingSubsets().

◆ setInPlaceOpOperand()

◆ wouldCreateReadAfterWriteInterference()

bool wouldCreateReadAfterWriteInterference ( OpOperand & operand,
const DominanceInfo & domInfo,
OneShotAnalysisState & state,
bool checkConsistencyOnly = false )
static

Return true if bufferizing operand inplace would create a conflict.

A read R and a write W of the same alias set is a conflict if inplace bufferization of W changes the value read by R to a value different from the one that would be expected by tracing back R's origin through SSA use-def chains. A conflict can only be introduced by a new alias and/or an inplace bufferization decision.

Example: %0 = tensor.extract_slice t[...][...][1, 1] {inplace?} %1 = vector.transfer_write v1, t {inplace} : vector<5xf32>, tensor<?xf32> e = tensor.extract_slice %1 %2 = vector.transfer_write v2, %0 {inplace} : vector<6xf32>, tensor<?xf32> %3 = vector.transfer_read e, cst : tensor<?xf32>, vector<7xf32>

In the above example, the two TransferWriteOps have already been decided to bufferize inplace. Bufferizing the ExtractSliceOp inplace would create a conflict because:

  • According to SSA use-def chains, we expect to read the result of %1.
  • However, adding an alias {%0, t} would mean that the second TransferWriteOp overwrites the result of the first one. Therefore, the TransferReadOp would no longer be reading the result of %1.

If checkConsistencyOnly is true, this function checks if there is a read-after-write conflict without bufferizing operand inplace. This would indicate a problem with the current inplace bufferization decisions.

Note: If checkConsistencyOnly, this function may be called with a null OpResult. In that case, only the consistency of bufferization decisions involving aliases of the given OpOperand are checked.

Definition at line 881 of file OneShotAnalysis.cpp.

References mlir::IROperand< DerivedT, IRValueT >::get(), getAliasingInplaceWrites(), getAliasingReads(), and hasReadAfterWriteInterference().

Referenced by bufferizableInPlaceAnalysisImpl(), and checkPreBufferizationAssumptions().

◆ wouldCreateWriteToNonWritableBuffer()

bool wouldCreateWriteToNonWritableBuffer ( OpOperand & operand,
OneShotAnalysisState & state,
bool checkConsistencyOnly = false )
static

Variable Documentation

◆ kBbArgAliasSetAttrName

StringLiteral kBbArgAliasSetAttrName = "__bbarg_alias_set_attr__"
constexpr

Definition at line 86 of file OneShotAnalysis.cpp.

Referenced by annotateOpsWithAliasSets().

◆ kInPlaceOperandsAttrName

StringLiteral kInPlaceOperandsAttrName = "__inplace_operands_attr__"
constexpr

Attribute marker to specify op operands that bufferize in-place.

Definition at line 81 of file OneShotAnalysis.cpp.

Referenced by setInPlaceOpOperand().

◆ kOpResultAliasSetAttrName

StringLiteral kOpResultAliasSetAttrName
constexpr
Initial value:
=
"__opresult_alias_set_attr__"

Definition at line 83 of file OneShotAnalysis.cpp.

Referenced by annotateOpsWithAliasSets().