[Mlir-commits] [mlir] [mlir][docs] Clarified Dialect creation tutorial + fixed typos (PR #77820)
llvmlistbot at llvm.org
llvmlistbot at llvm.org
Thu Jan 11 11:33:42 PST 2024
llvmbot wrote:
<!--LLVM PR SUMMARY COMMENT-->
@llvm/pr-subscribers-mlir-linalg
@llvm/pr-subscribers-mlir-llvm
Author: Perry Gibson (Wheest)
<details>
<summary>Changes</summary>
This PR adds clarification to the ["Creating a Dialect" tutorial](https://mlir.llvm.org/docs/Tutorials/CreatingADialect/) regarding how to register the dialect (especially globally).
The motivation for this came from trying to add my own dialect, and experiencing some friction since it had been a while.
[This forum post](https://discourse.llvm.org/t/how-to-register-a-dialect/66848/2) discusses the issue, but doesn't talk about the global reigstration approach.
[I created my own blogpost](https://gibsonic.org/blog/2024/01/11/new_mlir_dialect.html) which goes through a minimum working example, with stripped down TableGen files, but this level of detail might be overkill for this tutorial. However, I could add something like this if it is thought to be helpful
This PR also includes some spelling corrections across the mlir directory. The methodology for this was conservative, using the [codespell tool](https://github.com/codespell-project/codespell), and using my own discretion for correction. Corrections were only on comments and docs. To keep this PR small, only a fraction of the identified errors were corrected
---
Patch is 89.71 KiB, truncated to 20.00 KiB below, full version: https://github.com/llvm/llvm-project/pull/77820.diff
32 Files Affected:
- (modified) mlir/docs/DefiningDialects/_index.md (+15-15)
- (modified) mlir/docs/Tutorials/CreatingADialect.md (+10-4)
- (modified) mlir/include/mlir/Analysis/DataFlow/DenseAnalysis.h (+2-2)
- (modified) mlir/include/mlir/Analysis/DataFlow/IntegerRangeAnalysis.h (+1-1)
- (modified) mlir/include/mlir/Analysis/DataFlowFramework.h (+2-2)
- (modified) mlir/include/mlir/Analysis/Presburger/MPInt.h (+1-1)
- (modified) mlir/include/mlir/Analysis/Presburger/Matrix.h (+1-1)
- (modified) mlir/include/mlir/Analysis/Presburger/PWMAFunction.h (+2-2)
- (modified) mlir/include/mlir/Analysis/Presburger/PresburgerRelation.h (+1-1)
- (modified) mlir/include/mlir/Analysis/Presburger/Simplex.h (+4-4)
- (modified) mlir/include/mlir/Dialect/Affine/IR/AffineOps.h (+10-6)
- (modified) mlir/include/mlir/Dialect/Async/Passes.td (+3-3)
- (modified) mlir/include/mlir/Dialect/GPU/IR/CompilationInterfaces.h (+1-1)
- (modified) mlir/include/mlir/Dialect/GPU/IR/GPUBase.td (+2-2)
- (modified) mlir/include/mlir/Dialect/GPU/IR/GPUOps.td (+1-1)
- (modified) mlir/include/mlir/Dialect/GPU/TransformOps/GPUDeviceMappingAttr.td (+49-49)
- (modified) mlir/include/mlir/Dialect/LLVMIR/NVVMOps.td (+96-96)
- (modified) mlir/include/mlir/Dialect/LLVMIR/Transforms/Passes.td (+2-2)
- (modified) mlir/include/mlir/Dialect/Math/IR/MathOps.td (+1-1)
- (modified) mlir/include/mlir/Dialect/MemRef/IR/MemRefOps.td (+2-2)
- (modified) mlir/include/mlir/Dialect/MemRef/Transforms/Transforms.h (+1-1)
- (modified) mlir/include/mlir/Dialect/NVGPU/IR/NVGPU.td (+82-82)
- (modified) mlir/include/mlir/Dialect/NVGPU/Transforms/Transforms.h (+1-1)
- (modified) mlir/include/mlir/Dialect/SparseTensor/IR/Enums.h (+1-1)
- (modified) mlir/include/mlir/Dialect/SparseTensor/IR/SparseTensorOps.td (+4-4)
- (modified) mlir/include/mlir/Dialect/SparseTensor/Transforms/Passes.td (+1-1)
- (modified) mlir/include/mlir/ExecutionEngine/ExecutionEngine.h (+1-1)
- (modified) mlir/include/mlir/ExecutionEngine/MemRefUtils.h (+1-1)
- (modified) mlir/include/mlir/ExecutionEngine/SparseTensorRuntime.h (+1-1)
- (modified) mlir/python/mlir/dialects/func.py (+1-1)
- (modified) mlir/python/mlir/dialects/linalg/opdsl/lang/affine.py (+2-2)
- (modified) mlir/utils/emacs/mlir-lsp-client.el (+2-2)
``````````diff
diff --git a/mlir/docs/DefiningDialects/_index.md b/mlir/docs/DefiningDialects/_index.md
index 5a3993508fce88..78117a7f74358f 100644
--- a/mlir/docs/DefiningDialects/_index.md
+++ b/mlir/docs/DefiningDialects/_index.md
@@ -43,7 +43,7 @@ extends to all of the MLIR constructs, including [Interfaces](../Interfaces.md)
```tablegen
// Include the definition of the necessary tablegen constructs for defining
-// our dialect.
+// our dialect.
include "mlir/IR/DialectBase.td"
// Here is a simple definition of a dialect.
@@ -84,7 +84,7 @@ void MyDialect::initialize() {
The `summary` and `description` fields allow for providing user documentation
for the dialect. The `summary` field expects a simple single-line string, with the
-`description` field used for long and extensive documentation. This documentation can be
+`description` field used for long and extensive documentation. This documentation can be
used to generate markdown documentation for the dialect and is used by upstream
[MLIR dialects](https://mlir.llvm.org/docs/Dialects/).
@@ -133,7 +133,7 @@ void MyOp::setOtherValue(StringAttr newValue);
### Dependent Dialects
-MLIR has a very large ecosystem, and contains dialects that server many different purposes. It
+MLIR has a very large ecosystem, and contains dialects that serve many different purposes. It
is quite common, given the above, that dialects may want to reuse certain components from other
dialects. This may mean generating operations from those dialects during canonicalization, reusing
attributes or types, etc. When a dialect has a dependency on another, i.e. when it constructs and/or
@@ -230,7 +230,7 @@ is verified. The hook necessary for the dialect to implement has the form:
/// Verify the use of the given attribute, whose name is prefixed by the namespace of this
/// dialect, that was used on the attribute dictionary of a region entry block argument.
/// Note: As described above, when a region entry block has a dictionary is up to the individual
-/// operation to define.
+/// operation to define.
LogicalResult MyDialect::verifyRegionArgAttribute(Operation *op, unsigned regionIndex,
unsigned argIndex, NamedAttribute attribute);
```
@@ -250,7 +250,7 @@ has the form:
/// Generate verification for the given attribute, whose name is prefixed by the namespace
/// of this dialect, that was used on the attribute dictionary of a region result.
/// Note: As described above, when a region entry block has a dictionary is up to the individual
-/// operation to define.
+/// operation to define.
LogicalResult MyDialect::verifyRegionResultAttribute(Operation *op, unsigned regionIndex,
unsigned argIndex, NamedAttribute attribute);
```
@@ -258,8 +258,8 @@ LogicalResult MyDialect::verifyRegionResultAttribute(Operation *op, unsigned reg
### Operation Interface Fallback
Some dialects have an open ecosystem and don't register all of the possible operations. In such
-cases it is still possible to provide support for implementing an `OpInterface` for these
-operations. When an operation isn't registered or does not provide an implementation for an
+cases it is still possible to provide support for implementing an `OpInterface` for these
+operations. When an operation isn't registered or does not provide an implementation for an
interface, the query will fallback to the dialect itself. The `hasOperationInterfaceFallback`
field may be used to declare this fallback for operations:
@@ -269,10 +269,10 @@ field may be used to declare this fallback for operations:
void *MyDialect::getRegisteredInterfaceForOp(TypeID typeID, StringAttr opName);
```
-For a more detail description of the expected usages of this hook, view the detailed
+For a more detail description of the expected usages of this hook, view the detailed
[interface documentation](../Interfaces.md#dialect-fallback-for-opinterface).
-### Default Attribute/Type Parsers and Printers
+### Default Attribute/Type Parsers and Printers
When a dialect registers an Attribute or Type, it must also override the respective
`Dialect::parseAttribute`/`Dialect::printAttribute` or
@@ -286,7 +286,7 @@ parser and printer of its Attributes and Types it should set these to `0` as nec
### Dialect-wide Canonicalization Patterns
-Generally, [canonicalization](../Canonicalization.md) patterns are specific to individual
+Generally, [canonicalization](../Canonicalization.md) patterns are specific to individual
operations within a dialect. There are some cases, however, that prompt canonicalization
patterns to be added to the dialect-level. For example, if a dialect defines a canonicalization
pattern that operates on an interface or trait, it can be beneficial to only add this pattern
@@ -514,7 +514,7 @@ AbstractOperation::VerifyInvariantsFn verifyFn = [](Operation* op) {
AbstractOperation::ParseAssemblyFn parseFn =
[](OpAsmParser &parser, OperationState &state) {
// Parse the operation, given that the name is already parsed.
- ...
+ ...
};
// Printer function
@@ -526,14 +526,14 @@ auto printFn = [](Operation *op, OpAsmPrinter &printer) {
// General folder implementation, see AbstractOperation::foldHook for more
// information.
-auto foldHookFn = [](Operation * op, ArrayRef<Attribute> operands,
+auto foldHookFn = [](Operation * op, ArrayRef<Attribute> operands,
SmallVectorImpl<OpFoldResult> &result) {
...
};
// Returns any canonicalization pattern rewrites that the operation
// supports, for use by the canonicalization pass.
-auto getCanonicalizationPatterns =
+auto getCanonicalizationPatterns =
[](RewritePatternSet &results, MLIRContext *context) {
...
}
@@ -635,7 +635,7 @@ though overriden `parseType` methods need to add the necessary support for them.
```c++
Type MyDialect::parseType(DialectAsmParser &parser) const {
...
-
+
// The type name.
StringRef typeTag;
if (failed(parser.parseKeyword(&typeTag)))
@@ -649,7 +649,7 @@ Type MyDialect::parseType(DialectAsmParser &parser) const {
return dynType;
return Type();
}
-
+
...
}
```
diff --git a/mlir/docs/Tutorials/CreatingADialect.md b/mlir/docs/Tutorials/CreatingADialect.md
index af709fc46eff51..6ea56a0fcdefdd 100644
--- a/mlir/docs/Tutorials/CreatingADialect.md
+++ b/mlir/docs/Tutorials/CreatingADialect.md
@@ -10,10 +10,10 @@ Public dialects are typically separated into at least 3 directories:
* mlir/test/Dialect/Foo (for tests)
Along with other public headers, the 'include' directory contains a
-TableGen file in the [ODS format](../DefiningDialects/Operations.md), describing the
-operations in the dialect. This is used to generate operation
-declarations (FooOps.h.inc) and definitions (FooOps.cpp.inc) and
-operation interface declarations (FooOpsInterfaces.h.inc) and
+TableGen file in the [ODS format](../DefiningDialects/Operations.md),
+describing the operations in the dialect. This is used to generate
+operation declarations (FooOps.h.inc) and definitions (FooOps.cpp.inc)
+and operation interface declarations (FooOpsInterfaces.h.inc) and
definitions (FooOpsInterfaces.cpp.inc).
The 'IR' directory typically contains implementations of functions for
@@ -106,6 +106,12 @@ the LINK_COMPONENTS descriptor. This allows cmake infrastructure to
generate new library targets with correct linkage, in particular, when
BUILD_SHARED_LIBS=on or LLVM_LINK_LLVM_DYLIB=on are specified.
+Registration of the dialect can be performed globally by editing the
+file include/mlir/InitAllDialects.h. In this example, we can add
+`foo::FooDialect` to the `registry.insert` operation. This will
+make the dialect available to all MLIR programs which initiate their
+registries with `registerAllDialects` (e.g. mlir-opt). Alternatively,
+we can register the dialect locally in our required program.
# Dialect Conversions
diff --git a/mlir/include/mlir/Analysis/DataFlow/DenseAnalysis.h b/mlir/include/mlir/Analysis/DataFlow/DenseAnalysis.h
index 088b6cd7d698fc..b72d903a5edbe6 100644
--- a/mlir/include/mlir/Analysis/DataFlow/DenseAnalysis.h
+++ b/mlir/include/mlir/Analysis/DataFlow/DenseAnalysis.h
@@ -293,7 +293,7 @@ class DenseForwardDataFlowAnalysis
/// Base class for dense backward dataflow analyses. Such analyses attach a
/// lattice between the execution of operations and implement a transfer
-/// function from the lattice after the operation ot the lattice before it, thus
+/// function from the lattice after the operation on the lattice before it, thus
/// propagating backward.
///
/// In this implementation, a lattice attached to an operation represents the
@@ -426,7 +426,7 @@ class AbstractDenseBackwardDataFlowAnalysis : public DataFlowAnalysis {
/// A dense backward dataflow analysis propagating lattices after and before the
/// execution of every operation across the IR by implementing transfer
-/// functions for opreations.
+/// functions for operations.
///
/// `LatticeT` is expected to be a subclass of `AbstractDenseLattice`.
template <typename LatticeT>
diff --git a/mlir/include/mlir/Analysis/DataFlow/IntegerRangeAnalysis.h b/mlir/include/mlir/Analysis/DataFlow/IntegerRangeAnalysis.h
index 8bd7cf880c6afb..811ecf2835b268 100644
--- a/mlir/include/mlir/Analysis/DataFlow/IntegerRangeAnalysis.h
+++ b/mlir/include/mlir/Analysis/DataFlow/IntegerRangeAnalysis.h
@@ -92,7 +92,7 @@ class IntegerRangeAnalysis
public:
using SparseForwardDataFlowAnalysis::SparseForwardDataFlowAnalysis;
- /// At an entry point, we cannot reason about interger value ranges.
+ /// At an entry point, we cannot reason about integer value ranges.
void setToEntryState(IntegerValueRangeLattice *lattice) override {
propagateIfChanged(lattice, lattice->join(IntegerValueRange::getMaxRange(
lattice->getPoint())));
diff --git a/mlir/include/mlir/Analysis/DataFlowFramework.h b/mlir/include/mlir/Analysis/DataFlowFramework.h
index c76cfac07fc77a..1c594068fc8246 100644
--- a/mlir/include/mlir/Analysis/DataFlowFramework.h
+++ b/mlir/include/mlir/Analysis/DataFlowFramework.h
@@ -305,7 +305,7 @@ class DataFlowSolver {
/// these requirements.
///
/// 1. Querying the state of a program point prior to visiting that point
-/// results in uninitialized state. Analyses must be aware of unintialized
+/// results in uninitialized state. Analyses must be aware of uninitialized
/// states.
/// 2. Analysis states can reach fixpoints, where subsequent updates will never
/// trigger a change in the state.
@@ -462,7 +462,7 @@ class DataFlowAnalysis {
const DataFlowConfig &getSolverConfig() const { return solver.getConfig(); }
#if LLVM_ENABLE_ABI_BREAKING_CHECKS
- /// When compiling with debugging, keep a name for the analyis.
+ /// When compiling with debugging, keep a name for the analysis.
StringRef debugName;
#endif // LLVM_ENABLE_ABI_BREAKING_CHECKS
diff --git a/mlir/include/mlir/Analysis/Presburger/MPInt.h b/mlir/include/mlir/Analysis/Presburger/MPInt.h
index 12ab0598d10d99..fb95b6c19c487d 100644
--- a/mlir/include/mlir/Analysis/Presburger/MPInt.h
+++ b/mlir/include/mlir/Analysis/Presburger/MPInt.h
@@ -29,7 +29,7 @@ namespace presburger {
/// identically-named functions that operate on MPInts, which would otherwie
/// become the only candidates of overload resolution when calling e.g. ceilDiv
/// from the mlir::presburger namespace. So to access the 64-bit overloads, an
-/// explict call to mlir::ceilDiv would be required. These using declarations
+/// explicit call to mlir::ceilDiv would be required. These using declarations
/// allow overload resolution to transparently call the right function.
using ::mlir::ceilDiv;
using ::mlir::floorDiv;
diff --git a/mlir/include/mlir/Analysis/Presburger/Matrix.h b/mlir/include/mlir/Analysis/Presburger/Matrix.h
index 38fac50c13536e..1d454a598c6d43 100644
--- a/mlir/include/mlir/Analysis/Presburger/Matrix.h
+++ b/mlir/include/mlir/Analysis/Presburger/Matrix.h
@@ -46,7 +46,7 @@ class Matrix {
/// Construct a matrix with the specified number of rows and columns.
/// The number of reserved rows and columns will be at least the number
- /// specified, and will always be sufficient to accomodate the number of rows
+ /// specified, and will always be sufficient to accommodate the number of rows
/// and columns specified.
///
/// Initially, the entries are initialized to ero.
diff --git a/mlir/include/mlir/Analysis/Presburger/PWMAFunction.h b/mlir/include/mlir/Analysis/Presburger/PWMAFunction.h
index 236cc90ad66acd..6699f5469e4d16 100644
--- a/mlir/include/mlir/Analysis/Presburger/PWMAFunction.h
+++ b/mlir/include/mlir/Analysis/Presburger/PWMAFunction.h
@@ -117,7 +117,7 @@ class MultiAffineFunction {
/// The space of this function. The domain variables are considered as the
/// input variables of the function. The range variables are considered as
/// the outputs. The symbols parametrize the function and locals are used to
- /// represent divisions. Each local variable has a corressponding division
+ /// represent divisions. Each local variable has a corresponding division
/// representation stored in `divs`.
PresburgerSpace space;
@@ -239,7 +239,7 @@ class PWMAFunction {
/// The space of this function. The domain variables are considered as the
/// input variables of the function. The range variables are considered as
- /// the outputs. The symbols paramterize the function.
+ /// the outputs. The symbols parameterize the function.
PresburgerSpace space;
// The pieces of the PWMAFunction.
diff --git a/mlir/include/mlir/Analysis/Presburger/PresburgerRelation.h b/mlir/include/mlir/Analysis/Presburger/PresburgerRelation.h
index c6b00eca90733a..8a64e1e5ac799c 100644
--- a/mlir/include/mlir/Analysis/Presburger/PresburgerRelation.h
+++ b/mlir/include/mlir/Analysis/Presburger/PresburgerRelation.h
@@ -250,7 +250,7 @@ class PresburgerSet : public PresburgerRelation {
explicit PresburgerSet(const PresburgerRelation &set);
/// These operations are the same as the ones in PresburgeRelation, they just
- /// forward the arguement and return the result as a set instead of a
+ /// forward the argument and return the result as a set instead of a
/// relation.
PresburgerSet unionSet(const PresburgerRelation &set) const;
PresburgerSet intersect(const PresburgerRelation &set) const;
diff --git a/mlir/include/mlir/Analysis/Presburger/Simplex.h b/mlir/include/mlir/Analysis/Presburger/Simplex.h
index 9482f69b31cd66..6cb961057e1999 100644
--- a/mlir/include/mlir/Analysis/Presburger/Simplex.h
+++ b/mlir/include/mlir/Analysis/Presburger/Simplex.h
@@ -348,7 +348,7 @@ class SimplexBase {
SmallVector<UndoLogEntry, 8> undoLog;
/// Holds a vector of bases. The ith saved basis is the basis that should be
- /// restored when processing the ith occurrance of UndoLogEntry::RestoreBasis
+ /// restored when processing the ith occurrence of UndoLogEntry::RestoreBasis
/// in undoLog. This is used by getSnapshotBasis.
SmallVector<SmallVector<int, 8>, 8> savedBases;
@@ -371,7 +371,7 @@ class SimplexBase {
///
/// This does not directly support negative-valued variables, so it uses the big
/// M parameter trick to make all the variables non-negative. Basically we
-/// introduce an artifical variable M that is considered to have a value of
+/// introduce an artificial variable M that is considered to have a value of
/// +infinity and instead of the variables x, y, z, we internally use variables
/// M + x, M + y, M + z, which are now guaranteed to be non-negative. See the
/// documentation for SimplexBase for more details. M is also considered to be
@@ -565,7 +565,7 @@ struct SymbolicLexOpt {
/// negative for all values in the symbol domain, the row needs to be pivoted
/// irrespective of the precise value of the symbols. To answer queries like
/// "Is this symbolic sample always negative in the symbol domain?", we maintain
-/// a `LexSimplex domainSimplex` correponding to the symbol domain.
+/// a `LexSimplex domainSimplex` corresponding to the symbol domain.
///
/// In other cases, it may be that the symbolic sample is violated at some
/// values in the symbol domain and not violated at others. In this case,
@@ -756,7 +756,7 @@ class Simplex : public SimplexBase {
/// the ones marked redundant because we scan from left to right. Thus, when
/// there is some preference among the constraints as to which should be
/// marked redundant with priority when there are multiple possibilities, this
- /// could be accomplished by succesive calls to detectRedundant(offset,
+ /// could be accomplished by successive calls to detectRedundant(offset,
/// count).
void detectRedundant(unsigned offset, unsigned count);
void detectRedundant(unsigned offset) {
diff --git a/mlir/include/mlir/Dialect/Affine/IR/AffineOps.h b/mlir/include/mlir/Dialect/Affine/IR/AffineOps.h
index f070d048861906..34ce59bf870f00 100644
--- a/mlir/include/mlir/Dialect/Affine/IR/AffineOps.h
+++ b/mlir/include/mlir/Dialect/Affine/IR/AffineOps.h
@@ -117,7 +117,8 @@ class AffineDmaStartOp
/// Returns the affine map used to access the source memref.
AffineMap getSrcMap() { return getSrcMapAttr().getValue(); }
AffineMapAttr getSrcMapAttr() {
- return cast<AffineMapAttr>(*(*this)->getInherentAttr(getSrcMapAttrStrName()));
+ return cast<AffineMapAttr>(
+ *(*this)->getInherentAttr(getSrcMapAttrStrName()));
}
/// Returns the source memref affine map indices for this DMA operation.
@@ -156,7 +157,8 @@ class AffineDmaStartOp
/// Returns the affine map used to access the destination memref.
AffineMap getDstMap() { return getDstMapAttr().getValue(); }
AffineMapAttr getDstMapAttr() {
- return cast<AffineMapAttr>(*(*this)->getInherentAttr(getDstMapAttrStrName()));
+ return cast<AffineMapAttr>(
+ *(*this)->getInherentAttr(getDstMapAttrStrName()));
}
/// Returns the destination memref indices for this DMA operation.
@@ -185,7 +187,8 @@ class AffineDmaStartOp
/// Returns the affine map used to access the tag memref.
AffineMap getTagMap() { return getTagMapAttr().getValue(); }
AffineMapAttr getTagMapAttr() {
- return cast<AffineMapAttr>(*(*this)->getInherentAttr(getTagMapAttrStrName()));
+ return cast<AffineMapAttr>(
+ *(*this)->getInherentAttr(getTagMapAttrStrName()));
}
/// Returns the tag memref indices for this DMA operation.
@@ -201,7 +204,7 @@ class AffineDmaStartOp
getTagMap().getNumInputs());
}
- /// Impelements the AffineMapAccessInterface.
+ /// Implements the AffineMapAccessInterface.
/// Returns the AffineMapAttr associated with 'memref'.
NamedAttribute getAffineMapAttrForMemRef(Value memref) {
if (memref == getSrcMemRef())
@@ -307,7 +310,8 @@ class AffineDmaWaitOp
/// Returns the affine map used to access the tag memref.
AffineMap getTagMap() { return getTagMapAttr().getValue(); }
AffineMapAttr getTagMapAttr() {
- return cast<AffineMapAttr>(*(*this)->getInherentAttr(getTagMapAttrStrName()));
+ return cast<AffineMapAttr>(
+ *(*this)->getInherentAttr(getTagMapAttrStrName()));
}
/// Returns the tag memref index for this DMA operation.
@@ -321,7 +325,7 @@ class AffineDmaWaitOp
return cast<MemRefType>(getTagMemRef().getType()).getRank();
}
- /// Impelements the AffineMapAccessInterface. Returns the AffineMapAttr
+ /// Implements the AffineMapAccessInterface. Returns the AffineMapAttr
/// associated with 'memref'.
NamedAttribute getAffineMapAttrForMemRef(Value memref) {
assert(memref == getTagMemRef());
diff --git a/mlir/include/mlir/Dialect/Async/Passes.td b/mlir/include/mlir/Dialect/Async/Passes.td
index f0ef83ca3fd4f1..d4fbbf51907bc6 100644
--- a/mlir/include/mlir/Dialect/Async/Passes.td
+++ b/mlir/include/mlir/Dialect/Async/Passes.td
@@ -58,7 +58,7 @@ def AsyncFuncToAsyncRuntime : Pass<"async-func-to-async-runtime", "ModuleOp"> {
def AsyncRuntimeRefCounting : Pass<"async-runtime-ref-counting"> {
let summary = "Automatic reference counting for Async runtime operations";
let description = [{
- This pass works at the async runtime abtraction level, after all
+ This pass works at th...
[truncated]
``````````
</details>
https://github.com/llvm/llvm-project/pull/77820
More information about the Mlir-commits
mailing list