diff options
| author | Igor Wodiany <igor.wodiany@imgtec.com> | 2025-11-07 09:29:44 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-11-07 09:29:44 +0000 |
| commit | 7219b1e8a9f741e00f3a1952b66a4ed28d743ffe (patch) | |
| tree | 9558ca28aa2620efc73048c25716a29f6d7cc053 /lldb/source/Plugins/ScriptInterpreter/Python/Interfaces | |
| parent | 3a8f6979cef26ceb5ef5c6b8dba1fc1fd770c44c (diff) | |
| download | llvm-7219b1e8a9f741e00f3a1952b66a4ed28d743ffe.zip llvm-7219b1e8a9f741e00f3a1952b66a4ed28d743ffe.tar.gz llvm-7219b1e8a9f741e00f3a1952b66a4ed28d743ffe.tar.bz2 | |
[mlir][spirv] Enable validation of selection and phi tests (#166794)
Some of the test cases are failing as they introduce unstructured
control flow. It would be good to catch this in MLIR, but I am not sure
it is currently feasible. We could enforce the conditional branch to
always be in `spirv.mlir.selection` however from my perspective it will
break our downstream project as we rely on unstructured control flow,
i.e., the control flow graph is structured but we do not use
`spirv.mlir.selection` and `spirv.mlir.loop` as they do not currently
support early exists. It seems that the support for early exists is
slowly coming into MLIR so we probably can revise what is being enforced
regarding control flow ops in the future.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/Interfaces')
0 files changed, 0 insertions, 0 deletions