Update CUDA compat and add Metal #2108
Merged
Conversation
This file contains 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
|
Once the build has completed, you can preview your PR at this URL: https://julialang.netlify.app/previews/PR2108/ in ~15 minutes |
|
I was thinking the same - it made sense shoehorning when we just had the CUDA stuff. It feels a bit strange now. Can you factor out the GPU support into a separate table? Should Metal be 14+, given it is still early days for that package so we avoid legacy versions? |
|
This is the new table: |
|
cc @jpsamaroo @vchuravy. |
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.
cc @ViralBShah
I'm not sure shoehorning the GPU stuff in the existing table is the best way to go though. Maybe we need a separate table with accelerator-specific information (e.g., which GPU hardware) and their support tiers?