-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fft op crashes when being printing #1539
Comments
Was this hand-written or generated? I believe FftOp length must be 1-d:
|
Regradless shouldn't crash.. Likely something missing in the FftOp verifier. Will dig into this. |
It's based on an older MHLO test. Whatever the input is, it should error out gracefully instead of crashing, no? |
These require some stablehlo canonicalization patterns during lowering to IREE dialects. I also discovered some issues with the generic syntax (openxla/stablehlo#1539) and updated the tests to use the custom assembly format. Issue: #12678
These require some stablehlo canonicalization patterns during lowering to IREE dialects. I also discovered some issues with the generic syntax (openxla/stablehlo#1539) and updated the tests to use the custom assembly format. Issue: iree-org#12678
These require some stablehlo canonicalization patterns during lowering to IREE dialects. I also discovered some issues with the generic syntax (openxla/stablehlo#1539) and updated the tests to use the custom assembly format. Issue: iree-org#12678
This attribute now uses DenseI64ArrayAttr, so invalid representations of |
What happened?
The following snippet that uses the generic syntax crashes when printing:
Error message:
This works after changing the length to
tensor<1xi64>
. I'd expect either a verifier error or this print work.The equivalent code in the MHLO dialect prints fine: https://github.com/openxla/iree/blob/a8a70fb2dae68029fe7bdf159ed9353c7b531e1b/tests/e2e/xla_ops/fft.mlir
Steps to reproduce your issue
No response
Version information
mlir-hlo: git 65cc2df0392b3d0618fa70be8a10189760b7d30d, PiperOrigin-RevId: 534791162
The text was updated successfully, but these errors were encountered: