Magic-Mirror/llvm-capstone
1
0
Fork 0
mirror of https://github.com/capstone-engine/llvm-capstone.git synced 2025-03-02 07:16:29 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

[mlir][doc] Remove section about now removed useFoldAPI option

Browse Source
This commit is contained in:
Markus Böck 2023-02-24 00:25:17 +01:00
parent 7b79e8d455
commit 59343943cf
1 changed files with 0 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
mlir/docs/DefiningDialects/_index.md
View File

@ -255,31 +255,6 @@ LogicalResult MyDialect::verifyRegionResultAttribute(Operation *op, unsigned reg
unsigned argIndex, NamedAttribute attribute);
```
#### `useFoldAPI`
There are currently two possible values that are allowed to be assigned to this
field:
* `kEmitFoldAdaptorFolder` generates a `fold` method making use of the op's
`FoldAdaptor` to allow access of operands via convenient getter.
Generated code example:
```cpp
OpFoldResult fold(FoldAdaptor adaptor);
// or
LogicalResult fold(FoldAdaptor adaptor, SmallVectorImpl<OpFoldResult>& results);
```
* `kEmitRawAttributesFolder` generates the deprecated legacy `fold`
method, containing `ArrayRef<Attribute>` in the parameter list instead of
the op's `FoldAdaptor`. This API is scheduled for removal and should not be
used by new dialects.
Generated code example:
```cpp
OpFoldResult fold(ArrayRef<Attribute> operands);
// or
LogicalResult fold(ArrayRef<Attribute> operands, SmallVectorImpl<OpFoldResult>& results);
```
### Operation Interface Fallback
Some dialects have an open ecosystem and don't register all of the possible operations. In such