Add warnings on CUDA that compile or runtime performance may be affected - #180
Merged
Merged
Conversation
szymonlopaciuk
force-pushed
the
cuda-slow-warnings
branch
from
July 22, 2026 15:09
798f6c5 to
a2ac4a5
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Current behaviour of
ContextCupywith respect to automatic disabling of expensive optimisations is a bit opaque, and can be transparently enabled when not desired, but also not enabled when expected.This PR:
XO_CUDA_NO_FAST_COMPILEand the module-level switchxo.context_cupy.no_fast_compile, used to control this behaviour;XO_CUDA_NO_FAST_COMPILEis not given, but the current NVRTC version does not support disabling the optimisations, emits a warning to the user that they may need to update CUDA/NVRTC if compile performance is a problem.Additionally:
pre-commitso that the checks on CI and local match: currently this is not the case, which causes confusion.Checklist
Mandatory:
Optional: