Skip to content

Fix CUDA Extension Compilation and CPU Fallback Logic#6

Open
Electroiscoding wants to merge 1 commit intomainfrom
fix-cuda-extension-build-11700401904638269954
Open

Fix CUDA Extension Compilation and CPU Fallback Logic#6
Electroiscoding wants to merge 1 commit intomainfrom
fix-cuda-extension-build-11700401904638269954

Conversation

@Electroiscoding
Copy link
Copy Markdown
Owner

This pull request resolves an issue where the pip install xerv-crayon command would fail to compile the CUDA extension or crash the entire setup process.

By adding torch and numpy to the build-system requirements in pyproject.toml, pip correctly bootstraps the environment necessary for building PyTorch C++ extensions.

Furthermore, setup.py has been updated with a robust try...except SystemExit block. This ensures that if the system has CUDA but lacks proper paths or unsupported drivers (or any other compilation failure), the installation gracefully degrades to the AVX2/AVX-512 CPU-only backend instead of halting entirely.


PR created automatically by Jules for task 11700401904638269954 started by @Electroiscoding

- Added `torch` and `numpy` to `pyproject.toml` build-system requirements to ensure PyTorch is available for building the `CUDAExtension` during `pip install`.
- Updated `setup.py` to correctly catch `SystemExit` from failed `nvcc` compilation attempts, gracefully falling back to a CPU-only build instead of entirely failing the installation.
- Verified CPU fallback functionality via benchmarks and test suite.

Co-authored-by: Electroiscoding <103299713+Electroiscoding@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

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