-
Notifications
You must be signed in to change notification settings - Fork 651
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
why torch-to-iree pass generate func named main$async automatically? #17776
Comments
If you just want to convert from torch to linalg, use The |
THX, another question please, what should I do if I just want use python script to transform IR but not compile from source to use torch-mlir-opt? |
I have tried to conpile from source by using command line suggested: |
The IREE Python bindings expose some of the MLIR Python bindings (https://mlir.llvm.org/docs/Bindings/Python/) via
Please direct torch-mlir support questions to torch-mlir. Did you build after configuring? See https://github.com/llvm/torch-mlir/blob/main/docs/development.md#build-commands |
ok, I will try this. |
What happened?
When I try to use iree-opt --torch-to-iree to transform ir from torch to linalg. I found my function named main becomes main$async automatically. What should I do if I just want a function named main but not a async function named main$async?
Steps to reproduce your issue
What component(s) does this issue relate to?
MLIR
Version information
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: