-
Notifications
You must be signed in to change notification settings - Fork 44
1.12 #391
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
1.12 #391
Conversation
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Unfortunately, this is currently blocked by #384 and potentially other issues. I thought I could work around it using the khronos backend, but looks like that is broken in other ways |
src/device/quirks.jl
Outdated
| let BitInteger64 = Union{Int64, UInt64} | ||
| @device_override function Base.checkbounds(::Type{Bool}, v::StepRange{<:BitInteger64, <:BitInteger64}, i::BitInteger64) | ||
| @inline | ||
| return checkindex(Bool, eachindex(IndexLinear(), v), i) | ||
| end | ||
| end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| let BitInteger64 = Union{Int64, UInt64} | |
| @device_override function Base.checkbounds(::Type{Bool}, v::StepRange{<:BitInteger64, <:BitInteger64}, i::BitInteger64) | |
| @inline | |
| return checkindex(Bool, eachindex(IndexLinear(), v), i) | |
| end | |
| end | |
| BitInteger64 = Union{Int64, UInt64} | |
| @device_override function Base.checkbounds(::Type{Bool}, v::StepRange{<:BitInteger64, <:BitInteger64}, i::BitInteger64) | |
| @inline | |
| return checkindex(Bool, eachindex(IndexLinear(), v), i) | |
| end |
I don't think we can use let here and @device_override global function is not recognized by the macro. With this change and JuliaPackaging/Yggdrasil#12341 all tests are passing for me locally on 1.12
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’ll make the change and revert my temporary test-reducing measures shortly.
Should we also limit POCL to 7.0 for the main package instead of just tests until someone figures out what’s causing the new test failures?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need to restrict compatibility for the entire package. The issue is incomplete Float16 support, which we didnt test previously because the jlls had Float16 support disabled
Co-Authored-By: Simeon David Schaub <[email protected]>
This reverts commit 96b01c3.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't want to disable Float16 tests for the local pocl builds though, those should actually pass
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests are still failing which is what I was testing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PoCL local ones passed, e.g. https://github.com/JuliaGPU/OpenCL.jl/actions/runs/18655258708/job/53182708923
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's only on 1.10 and 1.11 though, not 1.12
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but the 1.12 failures are not due to Float16, they're #384 as I wrote earlier. Once the SPIRV-LLVM-Backend jll has been registered we can retrigger CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok I understand now thank you for bearing with me. I'll push a change to skip float16 only on pocl_jll and to revert to using spirv_llvm_translator as soon as it's registered
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I meant SPIRV-LLVM-Backend, not translator, so that part is already correct. I was just experimenting with the khronos translator, but it's still pretty broken atm
|
@simeonschaub I just noticed that the local builds don't report Float16 support. From the |
|
Ah, that's arm though, right? I believe only the x64 builds have |
|
Should we revert JuliaGPU/pocl@afa0682 and release pocl_jll v7.1.0+1? |
|
That commit is harmless, the one we might want to revert is JuliaGPU/pocl@893558a. But yes, that might be the best way forward Edit: opened JuliaPackaging/Yggdrasil#12355 |
|
Oops! I meant to link to the one you mentioned. |
|
Okay I think that when JuliaPackaging/Yggdrasil#12355 is registered and my suggestion reverting the check is applied, this will be ready to merge. the only question left is do we keep testing both 1.11 and 1.12 or only 1.12? Like in the original 1.12 pr? |
We already have way too many CI jobs in my opinion. I think we can just drop 1.11 since it's not an officially supported release anymore |
Co-authored-by: Christian Guinard <[email protected]>
|
I think the 1.12 macos runners just need more time. |
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can go ahead with this
Co-authored-by: Simeon David Schaub <[email protected]>
I wasn't comfortable force-pushing in #385 so I opened this one.