Skip to content
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.

Fix thrust linkage #1788

Closed
gevtushenko opened this issue Sep 5, 2022 · 2 comments
Closed

Fix thrust linkage #1788

gevtushenko opened this issue Sep 5, 2022 · 2 comments
Labels
P0: must have Absolutely necessary. Critical issue, major blocker, etc. thrust
Milestone
2.1.0

Comments

@gevtushenko
Copy link
Collaborator

The issue is related to the following one. It was recently addressed in CUB. Thrust has to inherit the namespace solution for the CUDA backend.
@gevtushenko gevtushenko added this to CCCL Sep 5, 2022
@gevtushenko gevtushenko added this to the 2.1.0 milestone Sep 5, 2022
@gevtushenko gevtushenko added the P0: must have Absolutely necessary. Critical issue, major blocker, etc. label Sep 5, 2022
@jrhemstad jrhemstad mentioned this issue Sep 9, 2022
Closed
@gevtushenko
Copy link
Collaborator Author

This seems to be needed in 1.17.X as well.

@jrhemstad
Copy link
Collaborator

I'm going to go ahead and say that we can fix this when we extra Thrust kernels into CUB and let's not bother worrying about fixing the kernels in Thrust. Feel free to reopen if you disagree.

@jrhemstad jrhemstad closed this as not planned Won't fix, can't repro, duplicate, stale Mar 7, 2023
@github-project-automation github-project-automation bot moved this to Done in CCCL Mar 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
P0: must have Absolutely necessary. Critical issue, major blocker, etc. thrust
Projects
CCCL
Archived in project
Milestone
2.1.0
Development

No branches or pull requests
2 participants
@gevtushenko @jrhemstad