ByteAddressBuffer Alignment proposal #557
Conversation
There was a problem hiding this comment.
The metadata needs to be updated and a sponsor found before we can assign a proposal number.
Maybe @amarpMSFT or @tex3d would be up for sponsoring?
There was a problem hiding this comment.
This looks ready to merge to me.
At this point we should be prioritizing getting the proposal merged - so it has a proposal number assigned etc.
Additional work - feedback, or fleshing out parts of the spec, can be tracked by github issues.
(This PR is working to try and clarify the process: #689)
There was a problem hiding this comment.
I've filed a number of follow-up issues and resolved comments in order to allow for this document to be assigned a number and merged.
In doing so, I also realized we might be better off splitting the AlignedLoad/AlignedStore HLSL intrinsics into a separate proposal. See #720.
For the remaining comments, please make corresponding changes or file more issues for future follow-up (like ones I've filed on other comments I resolved) and resolve them.
Before merging, you'll need to assign the next number to this proposal and rename the file. I've assumed 0050 in all my issues and links, so it would be great if we can use that number.
Then we can re-approve that version as necessary and merge the PR.
3 participants
Proposes a base alignment attribute for ByteAddressBuffer declarations and new templated Load/Store functions that include a relative alignment argument.