Add an extension for oneAPI.jl - #476
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #476 +/- ##
==========================================
- Coverage 84.14% 74.43% -9.71%
==========================================
Files 52 52
Lines 4674 4671 -3
==========================================
- Hits 3933 3477 -456
- Misses 741 1194 +453 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
d3e708a to
b33969a
Compare
|
@amontoison I'm starting to realize that there is quite a lot of redundant code between LapackCPU vs cuSOLVER vs rocSOLVER, etc. Wouldn't there be a better way? |
|
I think we can rely more on multiple dispatch. I can propose a unified API next week. The extension of oneAPI.jl is more a proof of concept than anything else because many things are still unstable in |
|
Should we add an Intel GPU runner? |
|
|
|
@michel2323, we don't have an Intel runner. Could you add one? |
|
Added oneAPI runner. @amontoison I forgot again how to resolve the CSR/CSC issue. |
|
@michel2323 Add a CSC format in |
|
@amontoison I'm hitting now a |
1289cda to
4c53da9
Compare
|
Your PR no longer requires formatting changes. Thank you for your contribution! |
|
@sshin23 After this, I can take care of making CUDA a MadNLPGPU extension too and try to consolidate the code for all three backends. |
8dc6c98 to
050a2ae
Compare
|
@michel2323 |
|
Because I forgot to commit the file 💩. |
No description provided.