-
Notifications
You must be signed in to change notification settings - Fork 27
Update to macOS SDK 26 and Metal 4 #290
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -137,14 +137,14 @@ | |
| } | ||
|
|
||
| # Non-standard versions; not included in bundle builds. | ||
| { | ||
| torchVersion = "2.8"; | ||
| cudaVersion = "12.4"; | ||
| cxx11Abi = true; | ||
| systems = [ | ||
| "x86_64-linux" | ||
| "aarch64-linux" | ||
| ]; | ||
| sourceBuild = true; | ||
| } | ||
| #{ | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Disabled, because we are now CUDA 12.6+. |
||
| # torchVersion = "2.8"; | ||
| # cudaVersion = "12.4"; | ||
| # cxx11Abi = true; | ||
| # systems = [ | ||
| # "x86_64-linux" | ||
| # "aarch64-linux" | ||
| # ]; | ||
| # sourceBuild = true; | ||
| #} | ||
|
Comment on lines
+140
to
+149
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is this expected ?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, see my comment above. We now only have CUDA 12.6 and up. Which means we finally have to make FA3 work with a newer CUDA version. |
||
| ] | ||
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.
if the user building the kernel don't have MetalToolchain installed would it be better to use
downloadComponentand get the toolchain and the path or just raise an error ?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 am not very keen on modifying the user's development environment outside the sandbox. Also, it will only result in half an install, because the toolchain mapping for the user is not set up (since the build runs as a non-privileged user).