Closed msluszniak closed 4 months ago
We killed the EXLA.Shape
module where this is happening. Does this still occur on main? That error would only fire if there was an issue getting a value from the dimensions tuple. The logic calls enif_get_tuple
and then cycles through enif_get_int64
calls. The only way it would fail is if the integer is out of bounds of the type, which it is not - so that's confusing.
I think this had even been fixed before by me somewhere along the way, and was basically a wrong integer size in the code path of creating EXLA.Shape
s
The following code
fives an error:
For smaller tensors like
Nx.iota({1000, 3})
the error does not occur.