-
Notifications
You must be signed in to change notification settings - Fork 42
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
char*
doesn't work
#716
Comments
Thanks for the report. This is an issue in clspv. I suggest you create an issue in the clspv project directly: https://github.com/google/clspv/issues. We can keep this one to track the need to update clspv when the fix lands. |
Definitely an issue with clspv. leaving the kernel options here
|
We only need to update clspv to fix that issue now. |
Should be fixed now |
thank you for your interest in my bug report. i appreciate the ongoing work being done. i compiled the latest main branch, however the issue persists with the exact same error on my machine. clspv version output:
|
I've just checked, and this is working on my side. Are you sure you have updated the submodules, and update |
my apologies, you are completely right! i had forgotten to update the submodules - i have taken care of it now. the opencl kernel compiled without issues! this time, though, i'm getting a strange runtime behaviour where the code i provided modifies the string as if it was an integer array (instead of incrementing the memory address by one for each index, it increments by four). to illustrate, here’s what happens when i iterate over the string:
notice how only every fourth element is modified, rather than a continuous string. i suspect this might be an aarch64-specific issue. can you give my modified example a try on your system? i attached my own output into thanks and regards |
This is definitively a bug in It is translating the following:
into:
|
while testing some OpenCL examples, i found out that
char*
is not working on my system (Raspberry Pi 5).code from hello_world.cl
it generates the following error
changing
__global char*
type to__global int*
resolves the issue.example source
The text was updated successfully, but these errors were encountered: