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
{{ message }}
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
I think the last hash value actually overflows because if you compute the hash manually it should be 15806800329040194030 * 2 + 9 ~ 3.1613601e+19 where 3.1613601e+19 > UINT64_MAX.
I was wondering if this overflow is a known behaviour?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
While working on issue (#20265).
I have noticed that hash values are overflowing uint64_t. I am working on the following code snippet from (https://github.com/apache/incubator-mxnet/blob/3480ba2c6df02bb907d3a975d354efa8697c4e71/tests/python/unittest/test_operator.py#L1707) where dim is fixed to 2 and num_groups = 2.
Hash computation is done here: https://github.com/apache/incubator-mxnet/blob/3480ba2c6df02bb907d3a975d354efa8697c4e71/src/operator/nn/mkldnn/mkldnn_convolution.cc#L387
I think the last hash value actually overflows because if you compute the hash manually it should be 15806800329040194030 * 2 + 9 ~ 3.1613601e+19 where 3.1613601e+19 > UINT64_MAX.
I was wondering if this overflow is a known behaviour?
Thanks,
Crefeda
Beta Was this translation helpful? Give feedback.
All reactions