1c535f1718
XLA implementation has this limitation and always uses 32 bit result for this instruction. This will cause mismatch between the result type in MLIR and XLA at the time of export. This should be resolved once we have a special dialect mapping directly to HLOInstructionProto. Another option until then could be to introduce a pass to legalize mhlo itself to match XLA semantics. PiperOrigin-RevId: 324286936 |
||
---|---|---|
include/mlir-hlo | ||
lib | ||
tests | ||
tools/mlir-hlo-opt |