-
Notifications
You must be signed in to change notification settings - Fork 187
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
Add documentation for Metal target #4262
Comments
Want to land before SIGGRAPH, but not critical for EOQ2 |
There's more detailed documentation needed here than I'd realized-- I'm going to need one of the authors of the Metal backend to assist. @ArielG-NV @jkwak-work @csyonghe |
We also should allow a user to choose the metal version being compiled with if we are to add |
@ArielG-NV , do we have a way to dump the name strings of profiles? Since there are a lot of profile names, I don't think we can list all of them on the document. |
Partially resolves shader-slang#4262 The description of "Parameter passing" part for Metal is related to PR
Partially resolves shader-slang#4262 The description of "Parameter passing" part for Metal is related to PR shader-slang#4022
Partially resolves shader-slang#4262 The description of "Parameter passing" part for Metal is related to PR shader-slang#4022
There currently is no way todo this.
I believe we could do both options. The idea I have in mind for documenting every capability/profile:
Related issue: #4125 |
Metal documentation is still very incomplete. |
Support for Metal should be documented as in prototype stage. Documentation must be added to docs/user-guide/09-targets.md to indicate that Metal is available as a work in progress (e.g. see note below CUDA and OptiX section). Additionally, it would be nice to document the format of the profile strings used by findProfile() in the appropriate places in docs/user-guide/08-compiling.md
The text was updated successfully, but these errors were encountered: