forked from OSchip/llvm-project
2d0477a003
When operations have optional attributes, or optional operands(i.e. empty variadic operands), the assembly format often has an optional section to represent these arguments. This revision adds basic support for defining an "optional group" in the assembly format to support this. An optional group is defined by wrapping a set of elements in `()` followed by `?` and requires the following:
* The first element of the group must be either a literal or an operand argument.
- This is because the first element must be optionally parsable.
* There must be exactly one argument variable within the group that is marked as the anchor of the group. The anchor is the element whose presence controls whether the group should be printed/parsed. An element is marked as the anchor by adding a trailing `^`.
* The group must only contain literals, variables, and type directives.
- Any attribute variables may be used, but only optional attributes can be marked as the anchor.
- Only variadic, i.e. optional, operand arguments can be used.
- The elements of a type directive must be defined within the same optional group.
An example of this can be seen with the assembly format for ReturnOp, which has a variadic number of operands.
```
def ReturnOp : ... {
let arguments = (ins Variadic<AnyType>:$operands);
// We only print the operands+types if there are a non-zero number
// of operands.
let assemblyFormat = "attr-dict ($operands^ `:` type($operands))?";
}
```
Differential Revision: https://reviews.llvm.org/D74681
|
||
|---|---|---|
| .. | ||
| AffineOps | ||
| Analysis | ||
| Conversion | ||
| Dialect | ||
| EDSC | ||
| Examples | ||
| IR | ||
| Pass | ||
| Quantizer | ||
| SDBM | ||
| Target | ||
| Transforms | ||
| Unit | ||
| lib | ||
| mlir-cpu-runner | ||
| mlir-cuda-runner | ||
| mlir-tblgen | ||
| mlir-vulkan-runner | ||
| APITest.h | ||
| CMakeLists.txt | ||
| lit.cfg.py | ||
| lit.site.cfg.py.in | ||