You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
I have found a strange behaviour when running an MLIR code through xdsl-opt (no passes). The code is a NN that has very large dense arrays, and so they are formatted as a string in hex. After running the code through xdsl-opt however, it replaces it by a single float, even though the tensor is multidimensional. A minimal example:
I added support for this back in January in #1974 , but it is quite likely that something was wrong there since the things I had to do to make it work were quite crusty.
Unassigning people just because that leads to a bit of a bystander effect, it would be great if one of the people previously assigned to assign the issue to themselves to communicate that they're looking into it. Seems like a bad bug that might bight us in the future. I can't really look into it for the next two weeks.
Hi there,
I have found a strange behaviour when running an MLIR code through xdsl-opt (no passes). The code is a NN that has very large dense arrays, and so they are formatted as a string in hex. After running the code through xdsl-opt however, it replaces it by a single float, even though the tensor is multidimensional. A minimal example:
After running it through
xdsl-opt
it will produce:The text was updated successfully, but these errors were encountered: