-
Notifications
You must be signed in to change notification settings - Fork 47
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
Version incompatibilities with the JuliaGPU stack #694
Comments
strides
not foundstrides
not found inside KernelAbstractions kernel
That was fixed here #692. |
You're right, AMDGPU is downgraded in the GPU CI, along with GPUArrays, GPUArraysCore and GPUCompiler. I can reproduce the error locally by setting
Same with trying to add AMDGPU instead - a clusterduck of version incompatibilities:
This is now not the same issue anymore, but would you know how to read these errors and what a fix could be? |
strides
not found inside KernelAbstractions kernel
This was because of the circular dependency between AK and AMDGPU, even though it does not really show in the above. I'll keep AK at 0.2 and defer updating the most significant version figure to when we coordinate in updating both sides. |
Ah, yes. I usually defer updating the version until the very moment I want to tag a release, this way it is easier for CI things. |
We recently set up a GPU CI for all the GPU backends of AcceleratedKernels.jl - it seems AMDGPU is the only platform where the call to
strides(::ROCArray)
fails inside a KernelAbstractions.jl kernel:A few notes: I know @pxl-th ran the N-dimensional reduction and it worked on his machine, but it may have been with GPUArraysCore=0.2. The ecosystem hasn't yet fully updated to that version, so I had to add
GPUArraysCore="0.1, 0.2"
to[compat]
- it may have been due to some combination of Adapt, Metal, and GPUArrays resulting in version conflicts.I can do a hacky fix and pass the strides to the kernel as an explicit argument, but I wanted to know if this is a known issue and where / how it could be solved.
The text was updated successfully, but these errors were encountered: