-
Notifications
You must be signed in to change notification settings - Fork 155
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
Use cuda::proclaim_return_type on device lambdas. #1314
Conversation
c704e99
to
ebddd5f
Compare
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.
Thanks @bdice !
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.
Thank you!
Looks like some device_vector ctor problems. |
f39e05c
to
7226804
Compare
The changes I pulled in were originally targeting CCCL 2 -- this branch can only use the |
/merge |
This PR updates cuspatial to CCCL 2.2.0. Do not merge until all of RAPIDS is ready to update. Follow-up to #1314. Authors: - Bradley Dice (https://github.com/bdice) Approvers: - Vyas Ramasubramani (https://github.com/vyasr) - Ray Douglass (https://github.com/raydouglass) - Robert Maynard (https://github.com/robertmaynard) - Mark Harris (https://github.com/harrism) URL: #1315
Description
This PR makes cuspatial compatible with Thrust 2 by adding
cuda::proclaim_return_type
, but does not upgrade the version of Thrust/CCCL just yet. Currently we use libcudacxx 2.1.0, which makescuda::proclaim_return_type
available, but we still use Thrust 1.17.2 which doesn't require device lambdas to have proclaimed return types. This diff is separated out from #1096. I will create a separate PR which contains only packaging changes / version updates for the CCCL 2 migration. This PR is nonbreaking, while the second PR will be breaking.Checklist