-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Build CuPy for PowerPC? #14
Comments
It seems we need conda-forge/nvcc-feedstock#21 to be closed first. |
The |
AnacondaRecipes/cudatoolkit-feedstock#6 is merged! |
Now we just need to figure out how to get the older versions in there 🙂 |
Can we build on top of CF's Power8 cudatoolkit instead? conda-forge/cudatoolkit-feedstock#6 |
Right now we are still building out |
@jakirkham How close we are to build for ppcle64? I lost track... |
Looks like updating pinning is the last missing piece? conda-forge/conda-forge-pinning-feedstock#725 |
Maybe @jaimergp would know 😉 |
Hi! Yes, it's been on my list for a while, but it got deprioritized after finding out OpenMM has some issues on GCC9+PPC, so I focused on other things while those are solved. I can work on it after I am done with conda-forge/nvcc-feedstock#59. IIRC, we need:
|
Note to self: cuSPARSELt currently does not support ppc64le. |
Hi all, I am reopening this issue for discussion. I've been monitoring CuPy's download counts regularly, and I noticed the download counts have been consistently on the order of 15 for every version (Python x CUDA) on ppc64le, making me suspect we have almost no human user of the ppc64le packages. If it's the case, we should consider to not build them so as to save CI and anaconda.org resources. |
Let me start by shrinking the build matrix for ppc64le. |
Continuing the discussion in cupy/cupy#2583 (comment).
@jakirkham @isuruf Do we have the compiler/docker/CI infrastructure for this task? A while ago I verified on Ascent (Summit's test node) that CuPy works on PowerPC, so it's just a matter of preparing and building.
cc: @berceanu
The text was updated successfully, but these errors were encountered: