This revision adds enough support to allow InlineAsmOp to work properly with indirect memory constraints "*m".
These require an explicit "elementtype" TypeAttr on the operands to pass LLVM verification and need to be provided.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
ok I see it now in https://buildkite.com/mlir/mlir-core/builds/20054#49efb465-9bb6-483e-8e92-4ab92560788d, looking
Comment Actions
This seems related to LLI + Intel SDE running through mlir-check.
Sent a patch that temporarily disables the LLI part of the test, the mlir-opt + mlir-translate is still a meaningful test: c2fa5ff5adba61dc5b0d477c0af1ea00ec2c596a.
Help to understand what is happening here would be appreciated.
Comment Actions
This is now fixed properly in 31b7f8857f4cd9c182b397ebf55db049318b3d7d: the test was not returning and would silently return non-0.
Thanks @bkramer for the correct hypothesis!