forked from OSchip/llvm-project
6ec3872845
Historically, custom builder specification in OpBuilder has been accepting the formal parameter list for the builder method as a raw string containing C++. While this worked well to connect the signature and the body, this became problematic when ODS needs to manipulate the parameter list, e.g. to inject OpBuilder or to trim default values when generating the definition. This has also become inconsistent with other method declarations, in particular in interface definitions. Introduce the possibility to define OpBuilder formal parameters using a TableGen dag similarly to other methods. Additionally, introduce a mechanism to declare parameters with default values using an additional class. This mechanism can be reused in other methods. The string-based builder signature declaration is deprecated and will be removed after a transition period. Reviewed By: jpienaar Differential Revision: https://reviews.llvm.org/D89470 |
||
|---|---|---|
| .. | ||
| dialect.td | ||
| expect-symbol.td | ||
| interfaces.mlir | ||
| llvm-intrinsics.td | ||
| op-attribute.td | ||
| op-decl.td | ||
| op-derived-attribute.mlir | ||
| op-error.td | ||
| op-format-spec.td | ||
| op-format.mlir | ||
| op-interface.td | ||
| op-operand.td | ||
| op-result.td | ||
| op-side-effects.td | ||
| openmp-common.td | ||
| pattern.mlir | ||
| predicate.td | ||
| return-types.mlir | ||
| rewriter-errors.td | ||
| testdialect-typedefs.mlir | ||
| trait.mlir | ||
| typedefs.td | ||
| types.mlir | ||