Metal documentation #5549
Metal documentation #5549
Conversation
There was a problem hiding this comment.
The purpose of 09-targets.md is to provide an overview of what each target platform expects, and less about what Slang will do on that platform.
We will use separate chapters for each platform to list all the details about how Slang translate different things to that platform.
We need a document that is similar to https://github.com/shader-slang/slang/blob/master/docs/user-guide/a2-01-spirv-target-specific.md for Metal.
In which we talk about every detail about the platform, including how types and specific intrinsics (atomics, texture fetching etc.) are translated.
expipiplus1
force-pushed
the
push-zmkqsoyltlmv
branch
from
541de8f
to
1e4101f
Compare
|
Can you please create a file that is under docs/user-guide/a2-02-metal-target-specific.md and move all the details there? Then we can deep link into this doc from shader-slang.com/docs |
expipiplus1
force-pushed
the
push-zmkqsoyltlmv
branch
from
1e4101f
to
e9ea5a7
Compare
|
I've added that file populated with the functionality from the metal legalization source. |
expipiplus1
force-pushed
the
push-zmkqsoyltlmv
branch
from
e9ea5a7
to
315bd3a
Compare
|
Thanks for the feedback, addressed. |
| [[mesh]] | ||
| void meshMain( | ||
| uint tid [[thread_position_in_grid]], | ||
| metal::mesh<VertexType, PrimitiveType, NumVertices, NumPrimitives, Topology> mesh |
There was a problem hiding this comment.
I think we support mesh shaders written in pure HLSL syntax without using metal specific types. Do we even have metal::mesh? This should be updated to reflect what is in tests\metal\simple-mesh.slang.
Closes #4262