-
Notifications
You must be signed in to change notification settings - Fork 88
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
Remove cuda cub #110
Remove cuda cub #110
Conversation
AppVeyor could no longer find packages. I followed recommendations for upgrading AppVeyor and hope that I didn't break anything badly. |
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.
I don't know how serious is the problem with cuda 7 and some GPUs, we can make it more explicit maybe as i suggested
LGTM, if someone manages to build it on a windoze system just to be sure we can merge. |
Well, it was "fixed" by asking AppVeyor for the "Visual Studio 2017" image instead of the "Visual Studio 2015" image. Other people have used "Previous Visual Studio 2015" as image. I hope that's good enough for now? |
# Conflicts: # CMakeLists.txt
Came across this- PR alicevision#110 . So I think this section is no longer correct. But searching the repo shows a couple of places where the flag is used in the cmake files- not sure if that needs cleanup, or I'm mistaken by the title of PR alicevision#110 .
This PR is meant to replace #103 . That PR attempts to fix a thrust::sort linker problem for sm5X that is due to an old bug in Thrust.
This is a simpler solution: CUB is removed entirely, the Thrust linker bug is fixed in an unexpected way: instead of fixing thrust::sort, just provide a StrictWeakOrdering operator implemented in a way that guarantees that it doesn't use any memory.