-
Notifications
You must be signed in to change notification settings - Fork 901
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
[FEA] Update to Thrust 1.16 #10841
Comments
Thanks for writing this up @robertmaynard! I can open the PRs for other repos soon - the time consuming part is self-review to make sure that the |
cugraph is now in progress rapidsai/cugraph#2310 |
So are cuML (rapidsai/cuml#4675), cuspatial (rapidsai/cuspatial#539), cuco (NVIDIA/cuCollections#161), raft (rapidsai/raft#678). I am planning to commit a custom rapids-cmake |
Depends on NVIDIA/cuCollections#165 and NVIDIA/cuCollections#171 This is a preparation step to finally address #10841. It fetches the latest version of `cuco` that [adds missing thrust headers ](NVIDIA/cuCollections#161) and [improves `static_map::retrieve_all`](NVIDIA/cuCollections#169). Authors: - Yunsong Wang (https://github.com/PointKernel) Approvers: - Bradley Dice (https://github.com/bdice) - Vyas Ramasubramani (https://github.com/vyasr) URL: #10983
This issue has been labeled |
Updates the bundled version of Thrust to 1.17.0. I will run benchmarks and include results in a comment below. Depends on #11457. Supersedes #10489, #10577, #10586. Closes #10841. **This should be merged concurrently with rapidsai/rapids-cmake#231 Authors: - Bradley Dice (https://github.com/bdice) Approvers: - David Wendt (https://github.com/davidwendt) - Nghia Truong (https://github.com/ttnghia) - Robert Maynard (https://github.com/robertmaynard) URL: #11437
We want to update the version of Thrust from 1.15 to 1.16 (changelog). This update is needed to fix compilation with GCC 11, because of some warnings-as-errors present in Thrust 1.15 with GCC 11 (such as this one from Thrust's copy of cub: NVIDIA/cub#418).
Describe the solution you'd like
As documented in #10586 the steps required are:
The text was updated successfully, but these errors were encountered: