-
Notifications
You must be signed in to change notification settings - Fork 925
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
Add pynvjitlink
as a dependency
#14763
Merged
rapids-bot
merged 19 commits into
rapidsai:branch-24.02
from
brandon-b-miller:add-pynvjitlink-dep
Jan 19, 2024
Merged
Changes from 1 commit
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
532da9f
add pynvjitlink to run_cudf
brandon-b-miller 02ef286
add pynvjitlink to meta.yaml for cudf
brandon-b-miller c6ae80c
unconditionally import patching function from pynvjitlink
brandon-b-miller 6c110b4
Merge branch 'branch-24.02' into add-pynvjitlink-dep
jakirkham 482be0f
Merge branch 'branch-24.02' into add-pynvjitlink-dep
brandon-b-miller d301cb9
add pynvjitlink to test_python_common
brandon-b-miller 8b8a12c
Fix pynvjitlink dependencies.
bdice aefd0c0
Remove testing dependency on pynvjitlink.
bdice c6b3982
Remove double suffix.
bdice c424796
Merge branch 'branch-24.02' into add-pynvjitlink-dep
brandon-b-miller 687225a
style
brandon-b-miller 92c6bb1
locally import patch_numba_linker
brandon-b-miller 7dbf9f2
update comment
brandon-b-miller e8a90b9
update comment
brandon-b-miller 698f1a2
Fix typo.
bdice 011038d
Merge branch 'branch-24.02' into add-pynvjitlink-dep
bdice b0972a9
Merge branch 'branch-24.02' into add-pynvjitlink-dep
bdice 016c237
Merge branch 'branch-24.02' into add-pynvjitlink-dep
brandon-b-miller d5c1efa
Merge branch 'branch-24.02' into add-pynvjitlink-dep
brandon-b-miller File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
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.
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.
Can we update the comment above to mention pynvjitlink and the corresponding role of that package? This comment:
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.
@brandon-b-miller I would generally advocate reviewing this entire file and any other files that relate to ptxcompiler/pynvjitlink to make sure things are named sensibly, etc. in a way that will support both CUDA 11 and CUDA 12+. I want the code comments and docs to reflect the implemented design going forward.
Keep in mind that we don't want to name things "CUDA 12" in the code if we can avoid it if it is likely that later versions will act in the same 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.
how about something like 7dbf9f2 ?
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.
Is this true? We don't use ptxcompiler in CUDA 12 environments. No environment should have both ptxcompiler and pynvjitlink installed at the same time.
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.
It's technically
_ptxcompiler.py
in this case - our slimmed down, vendored version of the few functions we need.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.
Ooooo. But I don't know how to distinguish
ptxcompiler
the package (only used when on CUDA 11) from_ptxcompiler.py
the internal helper file (always active) from the text of this comment. Documenting that kind of thing clearly is what I want to achieve before merging this.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.
some reworking in e8a90b9
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.
Much clearer! Thanks for iterating on this.