-
Notifications
You must be signed in to change notification settings - Fork 55
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
Update the wrappers for SuiteSparse 7 and remove cholmod_blas.h
bindings
#363
Conversation
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #363 +/- ##
==========================================
+ Coverage 93.85% 93.87% +0.01%
==========================================
Files 12 12
Lines 7473 7472 -1
==========================================
Hits 7014 7014
+ Misses 459 458 -1
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a small API change that was implemented in c09f0ac |
Even though the Manifest has the new SuiteSparse 7 in it, the generated wrappers are not picking up the new SuiteSparse 7:
|
I have updated I am not checking in the generated files, since they do not work - but they are essentially what I had in #362. |
I still get
We should doc how to develop and update a stdlib. |
It should be fine. I just checked the src of SuiteSparse: these changes are intended. |
Do you get that error using my PR as well? I really hope we can make SparseArrays.jl a standalone package and not an stdlib. cc @KristofferC |
Sorry. I finally understood the problem in #362 (comment) . I thought there were something wrong when Clang.jl mistakenly translated those Those "constants" are used in macros, so we need to either ignore the macro identifier or manually add those definitions like what we have done here: https://github.com/JuliaSparse/SparseArrays.jl/blob/main/src/solvers/LibSuiteSparse.jl#L11 |
To ignore a macro identifier, we can add it to this list: https://github.com/JuliaSparse/SparseArrays.jl/blob/main/gen/generator.toml#L9 For example,
|
Yes. This is the full version info:
I remembered that in the old days, to develop a stdlib, one simple hack is to manually edit the UUID of that package. I believe this hack can not work with the latest master? |
Yes, that's why I pinged @KristofferC here. I'm hoping that JuliaLang/julia#48979 will merge soon, which will make this a lot easier, and the next step is to remove SparseArrays from the stdlibs altogether. |
Is there any news? |
The wrappers need updating as discussed here. To ease the development of that, we now have merged JuliaLang/julia#48979, which removes SparseArrays from the Julia system image. |
Warning:
and failure on 32-bit Windows. |
I wouldn't worry about the failures here, which are using the nightly built on julia master. If it works locally, I think we should merge it, and then bump on Julia master, with some tender love and care. |
I should point out that I didn't test it locally. |
I did run the SparseArrays tests on a build of Julia that pulls in SuiteSparse 7 and SparseArrays.jl from this PR. Everything works fine, except for a couple of QR factorization failures for
cc @Wimmerer |
The missing ordering above is added by enabling PARTITION (METIS) support in SuiteSparse. JuliaPackaging/Yggdrasil#6446. |
@Gnimuc I think this doesn't treat the 32-bit OSes right. https://buildkite.com/julialang/julia-master/builds/22268#018714ca-ee8c-4b4e-a2d6-9a1fa3c6c7b2 |
The way to test is to use julia branch with the SuiteSparse 7 PR and update Since SparseArrays is no longer in the system image, you don't have to necessarily build Julia everytime you make a change. I think SparseArrays.jl/src/solvers/lib/i686-linux-gnu.jl Line 2408 in ee419ae
|
Trying in #372 |
As per the comment below, this problem does not seem to have been fixed in the new Julia 1.9.0 yet. Is there any reasonable time estimate as to when this problem might be fixed? |
We're trying to fix for 1.10. |
It looks like our old API in use is stable in SuiteSparse 7.cc @ViralBShah