build(infraCommons): bump for the fat CUDA architecture list - #71
Merged
Merged
Conversation
The toolchains now compile CUDA for every architecture the toolkit supports instead of the 75;80 pair, so newer GPUs get native SASS rather than PTX JIT. Also drops the caching commentary block from the workflow, which restated its env block (closes #70).
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.
Bumps infraCommons to ajakhotia/infraCommons#55: the toolchains now compile CUDA for every architecture CUDA 13.3 supports (sm_75 through sm_121, spelled out because OpenCV rejects CMake's special arch values) instead of the 75;80 pair, so newer GPUs get native SASS rather than PTX JIT. Validated by a full local lane (24.04 clang-shared) building and installing cleanly; fat per-TU objects keep ccache growth negligible (~0.3 GiB).
Also removes the caching commentary block above the workflow's docker run, which restated what its env block already shows. Closes #70.