-
Notifications
You must be signed in to change notification settings - Fork 16
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
[0018] SPIRV resource representation #98
Conversation
a5e3294
to
06203dc
Compare
f2f6821
to
d47c389
Compare
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.
This looks generally good to me, with a couple comments about the name of VulkanBuffer
and the use of spirv.DecoratedType
.
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.
LGTM, minor question.
I wonder what would be the stance on language-level intrinsincs for things like buffer which are not yet fully lowered, and highly represents an HLSL concept
structs have appropriate padding at the end to ensure its size is a multiple | ||
of its alignment. | ||
3. Matrix stride? | ||
4. Row major vs Col major? |
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 need to spend some time soon figuring out a design and plan for matrix types. There is a lot of complication there to figure out which will impact both DXIL and SPIRV.
Adds a proposal for how HLSL resources will be represented in llvm-ir when targeting SPIR-V.
1. Fix typos 2. Rename from `spv.*` to `spirv.*`
…ter_binding, and fix a couple minor errors.
0e2d541
to
a437cd9
Compare
Adds a proposal for how HLSL resources will be represented in llvm-ir
when targeting SPIR-V.