Support CUDA v6/CUDSS v0.7 and use cuSOLVER as dependency instead of CUDA#986
Merged
Conversation
5 tasks
cuSOLVER as dependency instead of CUDACUDA v6/CUDSS v0.7 and use cuSOLVER as dependency instead of CUDA
Contributor
Author
|
Note that the admins haven't decide whether to drop the extension of So currently, I only remove |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist
contributor guidelines, in particular the SciML Style Guide and
COLPRAC.
This PR directly set
cuSOLVERas dependency for the extension instead of the entireCUDApackage.It still works if users load
CUDA v6, since it internally loadscuSOLVER, too.This PR also includes the changes in PR #983