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
Hi, I find if use directly 4 8 bit int in integer as following link, it will cause compiling error (when the member of int is referred as .s0, .s1 later) in my opencl compiler provided by my vendor. I am wondering whether the paradigm is legal in the specific opencl spec version or it should be fixed to use char4 instead.
areusch
removed
the
needs-triage
PRs or issues that need to be investigated by maintainers to find the right assignees to address it
label
Nov 16, 2022
Hi, I find if use
directly 4 8 bit int in integer
as following link, it will cause compiling error (when the member of int is referred as .s0, .s1 later) in my opencl compiler provided by my vendor. I am wondering whether the paradigm is legal in the specific opencl spec version or it should be fixed to usechar4
instead.https://github.com/apache/incubator-tvm/blob/952def53da51e6cf17c5dbf50b92e193622ca695/src/target/source/codegen_opencl.cc#L125
The text was updated successfully, but these errors were encountered: