-
Notifications
You must be signed in to change notification settings - Fork 24.1k
[Reland2] Update NVTX to NVTX3 #109843
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
[Reland2] Update NVTX to NVTX3 #109843
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/109843
Note: Links to docs will display an error until the docs builds have been completed. ❌ 6 New Failures, 3 Unrelated FailuresAs of commit 8b303bd with merge base 0a25666 ( NEW FAILURES - The following jobs have failed:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
UNSTABLE - The following jobs failed but were likely due to flakiness present on trunk and has been marked as unstable:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
b2eaaf7
to
d260ed6
Compare
@izaitsevfb This PR combines your changes in #107497 and more cleanups. And I chose to include 'nvtx3/XXX' to avoid confusion and linking issues between old and newer versions of NVTX. |
@pytorchbot label "topic: not user facing" |
f9d1d49
to
eebcc4b
Compare
@pytorchbot label ciflow/binaries |
65f5805
to
52c1190
Compare
Windows test hosts must install NVTX3 before we can continue. I proposed a PR at pytorch/builder#1547 |
@pytorchbot rebase |
472ac1b
to
823cee6
Compare
Co-authored-by: Ivan Zaitsev <[email protected]>
@pytorchmergebot merge -f "Rocm 6.0 was removed" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Another attempt to update NVTX to NVTX3. We now avoid changing NVTX header inclusion of existing code. The advantage of NVTX3 over NVTX is that it is a header-only library so that linking with NVTX3 can greatly simplify our CMake and other building scripts for finding libraries in user environments. In addition, NVTX are indeed still present in the latest CUDA versions, but they're no longer a compiled library: It's now a header-only library. That's why there isn't a .lib file anymore. Pull Request resolved: #109843 Approved by: https://github.com/peterbell10, https://github.com/eqy Co-authored-by: Ivan Zaitsev <[email protected]>
Another attempt to update NVTX to NVTX3. We now avoid changing NVTX header inclusion of existing code. The advantage of NVTX3 over NVTX is that it is a header-only library so that linking with NVTX3 can greatly simplify our CMake and other building scripts for finding libraries in user environments. In addition, NVTX are indeed still present in the latest CUDA versions, but they're no longer a compiled library: It's now a header-only library. That's why there isn't a .lib file anymore.
cc @malfet @seemethere @izaitsevfb @peterbell10