-
Notifications
You must be signed in to change notification settings - Fork 50
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
Fatal error of resnet18 example in README #77
Comments
I found out that from the beginning, which I mean the mlir program generated from torch-mlir, has this generic op, which input and output are in different shapes as this:
But because the sizes are both 1, so it'll apply the pattern Furthermore, the resnet18 stucked at the pass
here, which will only examine if isValidDim is true. Change to this fix the error:
The other three CNNs don't have the same problem as resnet18 because they don't have such GenericOp from torch-mlir and there is no integer op. I put all the changes in my forked repo and opened this PR, hope it looks good to you. P.S.
|
If I modify it as you suggested, I find that new issues arise. I suspect that the current versions of torch-mlir and scalehls might not be fully compatible, but I'm not sure which version would be more appropriate. If it's convenient for you, could you share your environment setup? I would greatly appreciate it |
The versions could be most likely the issue here. I tried the "ScaleHLS 2.0" as well and the same problem still exists. I haven't work on this for quite a while, but I hope this list would help you:
And python version is 3.11.9 ;) |
As title I've run into this error when trying to use the scaleflow-pytorch-pipeline on the generated mlir code.
I add the debug-point option into the pipeline and trace this error to
SimplifyCopyPass
, in which amemref.copy
will be created usingin
andout
fromlinalg.generic
. And as you can see above, they are not in the same shape.So I wonder the issue behind this is either the GenericOp is wrong or the pass is. Or maybe even because of wrong version of torch-mlir?
I hope the contributors of this repo could help ;D @hanchenye @signorgelato @jeonghm9764
The text was updated successfully, but these errors were encountered: