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.
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
Update for CUDA 12.2.2 #32
Update for CUDA 12.2.2 #32
Changes from all commits
281f422
b330aca
f3fc3c7
8af24b0
ecf3a3e
5a2894e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also add a
cuda-crt-dev
either here or incuda-nvcc-impl
, which pulls incuda-crt-dev_{{ target_platform }}
? This may also be a bit more ergonomicThis would be somewhat similar to what we did with
cuda-cudart-dev
. Though that has a few more pieces to pull inUnderstand if this feels redundant. Mainly wanted to surface the suggestion so we could make a decision either way
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have strong opinions here. I am okay with the current implementation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same, no strong opinion here. All of these details should be hidden from the user anyway, so I'd say we hold off on adding more packaging indirection until we see more benefits for us as maintainers. Right now I think the tradeoff of clarity for volume is pretty even.