Skip to content

spconv: Add version 2.3.8 - #4916

Draft
luhenry wants to merge 2 commits into
mainfrom
spconv
Draft

luhenry wants to merge 2 commits into
mainfrom
spconv

Conversation

@luhenry

@luhenry luhenry commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Compiles a CPU-only spatially-sparse-convolution extension via pccm/cumm code generation. Upstream publishes no riscv64 wheel.

Follows upstream's documented CPU-only build recipe (README: pip install spconv for CPU only, Linux only); upstream ships no public CI workflow to mirror.

Differs from upstream

  • Build-from-checkout, not sdist - upstream publishes no sdist for this package.
  • Nothing beyond the riscv64 image and pulling cumm from our own registry.

Testing

  • Smoke import only (import spconv) - import spconv.algo is excluded: it unconditionally imports the CUDA-gated cumm.gemm.main/cumm.conv.main pccm units, which setup.py never compiles into a CPU-only build (confirmed against upstream's own published PyPI CPU wheel, which has the identical gap). Not importable in any CPU-only build of this version, riscv64 included.
  • Upstream's own suite is CUDA/MNIST-oriented and does not apply to the CPU-only build its own README documents as debug-only.

License: OK - Apache-2.0, LICENSE bundled automatically by setuptools, nothing vendored.

Blocked on cumm (now published) until this PR; riscv64 CI pending on this PR's first run.

Build-from-checkout, mirroring upstream's documented CPU-only install
path (SPCONV_DISABLE_JIT=1, CUMM_CUDA_VERSION empty). Depends on cumm
(cumm>=0.7.11,<0.8.0), now published on pypi.riseproject.dev, via
PIP_EXTRA_INDEX_URL. Local x86_64 rehearsal (public cumm 0.7.11 CPU
wheel + --no-build-isolation) built cleanly; a pybind11 ABI mismatch
between that older public cumm wheel and a freshly-installed pybind11
surfaced during the rehearsal's deeper smoke import, unrelated to
this package's own build mechanics -- see the .queue.yml note for
detail and what to check if riscv64 CI hits the same symptom against
our own cumm wheel.
@luhenry
luhenry marked this pull request as draft November 17, 2026 23:49
Real riscv64 CI (run 44202562155, job 134460257373): all 4 build legs
(cp310-cp313) built, auditwheel-repaired and installed fine, then died
at the test step with ModuleNotFoundError: No module named
'spconv.core_cc.cumm.conv'; 'spconv.core_cc.cumm' is not a package.

Confirmed against the real upstream source, not guessed: cloned
traveller59/spconv v2.3.8's setup.py only adds the cu/convcu pccm
units (namespaces cumm.gemm.main/cumm.conv.main) to the extension when
CUMM_CPU_ONLY_BUILD is false; cumm v0.7.11's own constants.py forces
that flag true whenever CUMM_CUDA_VERSION is set to an empty string,
exactly what CIBW_ENVIRONMENT already sets per upstream's documented
CPU-only recipe. spconv/algo.py imports both at module level with no
CPU-only guard, so `import spconv.algo` fails in any CPU-only build.

Downloaded and unzipped the official PyPI spconv==2.3.8 manylinux
x86_64 wheel to confirm this is not riscv64-specific: its core_cc .pyi
stub tree has no cumm/conv or cumm/gemm entries either, matching this
build exactly. Our riscv64 wheel is behaving identically to upstream's
own published CPU wheel; drop the module from the smoke test rather
than chase a gap that is not ours to fix.

Signed-off-by: Ludovic Henry <git@ludovic.dev>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant