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
Apparently both char and cuchar are unsigned on this platform, so we need to fix how Int8 intrinsics are mangled (or use different intrinsics for Int8). Probably by checking how an int8_t call (which I presume is still signed on linux-aarch64) is compiled by OpenCL compilers.
The text was updated successfully, but these errors were encountered:
Apparently what makes things even more complicated is that this is really compiler-dependent (as most types in C), not just platform: https://stackoverflow.com/a/20576301 suggests that this can be changed with an option in XCode for macOS platforms, and there's an llvm option to choose the signedness of char.
Apparently both
char
andcuchar
are unsigned on this platform, so we need to fix howInt8
intrinsics are mangled (or use different intrinsics forInt8
). Probably by checking how anint8_t
call (which I presume is still signed on linux-aarch64) is compiled by OpenCL compilers.The text was updated successfully, but these errors were encountered: