Théo Degioanni 69d3ba3db9 [mlir][irdl] Introduce names in IRDL value lists (#123525) ...

In order to meaningfully generate getters and setters from IRDL, it
makes sense to embed the names of operands, results, etc. in the IR
definition. This PR introduces this feature. Names are constrained
similarly to TableGen names.

2025-01-19 21:58:52 +01:00

..

include

…

Library

…

apply-foreach-nested.mlir

…

check-use-after-free.mlir

…

expensive-checks.mlir

…

foreach-match.mlir

…

infer-effects.mlir

…

interpreter-entry-point.mlir

…

interpreter.mlir

…

irdl.mlir

[mlir][irdl] Introduce names in IRDL value lists (#123525)

2025-01-19 21:58:52 +01:00

multi-arg-top-level-ops.mlir

…

multi-arg-top-level-params.mlir

…

multi-arg-top-level-values.mlir

…

ops-invalid.mlir

…

ops.mlir

…

preload-library-invalid.mlir

…

preload-library.mlir

…

selective-targeting.mlir

…

test-dialect-injection.mlir

…

test-interpreter-debug.mlir

…

test-interpreter-external-concurrent.mlir

…

test-interpreter-external.mlir

…

test-interpreter-printing.mlir

…

test-interpreter.mlir

make transform.split_handle accept any handle kind (#118752)

2024-12-15 22:58:16 +01:00

test-loop-transforms.mlir

…

test-pass-application.mlir

…

test-pattern-application.mlir

…

test-pdl-extension.mlir

…

transform-state-extension-initializer.mlir

…

transform-state-extension.mlir

…