-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Op][Topi] 5 ops can accept unsigned integers as indices #10098
[Op][Topi] 5 ops can accept unsigned integers as indices #10098
Conversation
Debugging I've worked the issue to likely |
#10102 <-- fix here. There is another error now with unravel index now though. You can try digging more, or you can drop unravel_index for later PR (which I recommend) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM mostly, just lmk the plan to deal with unravel_index
Thanks for your help! I prefer to drop unravel_index and open a PR later. |
…ops-indexing-support-uint
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* tests passed * reformat * add uint test for unravel_index
Hello community,
This PR links to #10064. 5 ops (scatter, scatter_add, scatter_nd, unravel_index, adv_index) accept unsigned integers as indices. Somehow unravel_index with uint indices may raise
in function
tvm/src/arith/const_int_bound.cc
Line 486 in e6af874
I tried to figure out why shape[v] can be 0 in
tvm/include/tvm/topi/transform.h
Line 383 in 7b9fd1e
but I failed to understand.
Thank reviewers for your help and your time speeding in CR.
cc @AndrewZhaoLuo