Drop Maxwell (sm50) build from distribution #1755
Merged
Conversation
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
matthewdouglas added CUDA 
| The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
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.
This PR removes support for NVIDIA Maxwell GPUs (sm50/sm52) in our normal binary distribution. The README and documentation have been updated to reflect this change. There are some other minor corrections to the documentation.
These GPUs are >= 10 years old now. This includes models such as GTX 980, M4, and Quadro M6000. We're making this change as user demand for continued Maxwell support has been very limited, and this will reduce our maintenance and binary size overhead.
For the time being, support for Maxwell GPUs can still be built from source, but we will not continue to guarantee or maintain that compatibility moving forward.
This change is targeted to be included in the upcoming v0.48.0 release.