diff options
| author | Razvan Lupusoru <razvan.lupusoru@gmail.com> | 2025-02-12 14:13:45 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-02-12 14:13:45 -0800 |
| commit | ceb00c07028491506bcf8e334bb12cab7792098f (patch) | |
| tree | 955c522b5795101db76342833e95fa56e251107f /mlir/lib/Bytecode | |
| parent | c5a4512d853d7d2deef2080b1acb6272fa683bc3 (diff) | |
[mlir][acc] Clean up TypedValue builders (#126968)
When MappableType was introduced alongside PointerLikeType, the data
clause operation builders were duplicated to accept a `TypedValue` of
one of the two type options. However, the underlying builder takes a
`Value` and this difference is not relevant for it. The only difference
is that `varType` is set differently depending on the type.
Having two duplicated builders can lead to clunky building since a
`Value` must always be cast to one of the two options. Thus, simply
clean this up - the verifier already checks that it is a type that
implements one of the two interfaces.
Diffstat (limited to 'mlir/lib/Bytecode')
0 files changed, 0 insertions, 0 deletions
