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
initially suspected int32 overflow but 134M << 2**31
Meta comment. The reproducer took 2 hours to make because jnp.cumsum was used inside ~400 lines of code, and I wrongly assumed jnp.cumsum was unlikely to cause segment fault compared to: tesseleate-ipu, C code, usage of uint in C code, poplar simulation of uint64 in C code, passing from python to C code, index computations, ... . Would it be a lot of work to add automated testing on these basic (np, jnp) functions?
What jax/jaxlib version are you using?
0.3.16
Which accelerator(s) are you using?
IPU MK2
Additional System Info
No response
The text was updated successfully, but these errors were encountered:
Here's a hacky temporary solution. It uses matrix multiplication to compute jnp.cumsum of 2**7 chunks, and then subsequently adds the correct offsets. Use with caution. >90% of time is spent adding the subsequent offsets.
Description
Reproducer
Output
Note:
Meta comment. The reproducer took 2 hours to make because
jnp.cumsum
was used inside ~400 lines of code, and I wrongly assumedjnp.cumsum
was unlikely to cause segment fault compared to: tesseleate-ipu, C code, usage of uint in C code, poplar simulation of uint64 in C code, passing from python to C code, index computations, ... . Would it be a lot of work to add automated testing on these basic (np, jnp) functions?What jax/jaxlib version are you using?
0.3.16
Which accelerator(s) are you using?
IPU MK2
Additional System Info
No response
The text was updated successfully, but these errors were encountered: