-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
taichi_ngp example fails on master #6978
Labels
bug
We've confirmed that this is an BUG
Comments
Yep. I'll send a fix for it. |
strongoier
added a commit
that referenced
this issue
Jan 6, 2023
PGZXB
pushed a commit
to PGZXB/taichi
that referenced
this issue
Jan 6, 2023
…aichi-dev#7068) Issue: taichi-dev#6978, fix taichi-dev#6902 Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
strongoier
added a commit
that referenced
this issue
Jan 9, 2023
Issue: fix #6978 ### Brief Summary After #7068, The `taichi_ngp` example reports `RuntimeError: [type_factory.cpp:promoted_type@222] Assertion failure: a->is<TensorType>() && b->is<TensorType>()`. The root cause is that `taichi_ngp` uses `atomic_sub` on a value with type different from the destination, which will generate `neg` + `cast`. However, the `ret_type` and `cast_type` of `UnaryOpStmt` produced by `Scalarize` aren't set correctly. This PR fixes the problem.
lin-hitonami
pushed a commit
to lin-hitonami/taichi
that referenced
this issue
Jan 9, 2023
…aichi-dev#7068) Issue: taichi-dev#6978, fix taichi-dev#6902 Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
lin-hitonami
pushed a commit
to lin-hitonami/taichi
that referenced
this issue
Jan 9, 2023
…dev#7082) Issue: fix taichi-dev#6978 ### Brief Summary After taichi-dev#7068, The `taichi_ngp` example reports `RuntimeError: [type_factory.cpp:promoted_type@222] Assertion failure: a->is<TensorType>() && b->is<TensorType>()`. The root cause is that `taichi_ngp` uses `atomic_sub` on a value with type different from the destination, which will generate `neg` + `cast`. However, the `ret_type` and `cast_type` of `UnaryOpStmt` produced by `Scalarize` aren't set correctly. This PR fixes the problem.
lin-hitonami
pushed a commit
to lin-hitonami/taichi
that referenced
this issue
Jan 12, 2023
…aichi-dev#7068) Issue: taichi-dev#6978, fix taichi-dev#6902 Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
lin-hitonami
pushed a commit
to lin-hitonami/taichi
that referenced
this issue
Jan 12, 2023
…dev#7082) Issue: fix taichi-dev#6978 ### Brief Summary After taichi-dev#7068, The `taichi_ngp` example reports `RuntimeError: [type_factory.cpp:promoted_type@222] Assertion failure: a->is<TensorType>() && b->is<TensorType>()`. The root cause is that `taichi_ngp` uses `atomic_sub` on a value with type different from the destination, which will generate `neg` + `cast`. However, the `ret_type` and `cast_type` of `UnaryOpStmt` produced by `Scalarize` aren't set correctly. This PR fixes the problem.
quadpixels
pushed a commit
to quadpixels/taichi
that referenced
this issue
May 13, 2023
…aichi-dev#7068) Issue: taichi-dev#6978, fix taichi-dev#6902 Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
quadpixels
pushed a commit
to quadpixels/taichi
that referenced
this issue
May 13, 2023
…dev#7082) Issue: fix taichi-dev#6978 ### Brief Summary After taichi-dev#7068, The `taichi_ngp` example reports `RuntimeError: [type_factory.cpp:promoted_type@222] Assertion failure: a->is<TensorType>() && b->is<TensorType>()`. The root cause is that `taichi_ngp` uses `atomic_sub` on a value with type different from the destination, which will generate `neg` + `cast`. However, the `ret_type` and `cast_type` of `UnaryOpStmt` produced by `Scalarize` aren't set correctly. This PR fixes the problem.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It works in v1.3 and now fails with
Seems to be related to the slicing behavior of matrix. cc: @jim19930609 @strongoier
The text was updated successfully, but these errors were encountered: