The bug was not noticed because we didn't have a lot of custom type conversions
directly to LLVM dialect.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
It looks like it would require using TestDialect and writing a test pass from test dialect to llvm. Could there be a simpler way of testing this?
Comment Actions
It looks like it would require using TestDialect and writing a test pass from test dialect to llvm. Could there be a simpler way of testing this?
How did you stumble upon this? I think this function is called when an std.call is converted, so it should be sufficient to test that an std.call to a function that takes a mix of memrefs and scalars as arguments.
Comment Actions
The mix of memrefs and scalars (with STD types) does not do the trick. I stumbled upon this bug when I tried to call a function that has a custom non-std type. In my case it was !tf_framework.op_kernel_context.