Skip to content

[0035] Clarify matrix descriptor bounds checking granularity - #923

Merged
Damyan Pepper (damyanp) merged 1 commit into
microsoft:mainfrom
damyanp:damyanp-matrix-bounds-checking
Aug 31, 2026
Merged

[0035] Clarify matrix descriptor bounds checking granularity#923
Damyan Pepper (damyanp) merged 1 commit into
microsoft:mainfrom
damyanp:damyanp-matrix-bounds-checking

Conversation

@damyanp

Copy link
Copy Markdown
Member

Clarify that per-element bounds checking for linear algebra matrix descriptor loads and writes operates at 4-byte granularity, consistent with (RW)ByteAddressBuffer\ size alignment.

Also fix a typo in the existing store bounds-checking text.

Assisted by GitHub Copilot.

Specify that per-element bounds checks operate at 4-byte granularity for descriptor loads and writes.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: ecca7b42-1fbe-4dc2-9e6b-c739199ffede
@damyanp
Damyan Pepper (damyanp) marked this pull request as ready for review August 27, 2026 17:31
@damyanp Damyan Pepper (damyanp) changed the title Clarify matrix descriptor bounds checking granularity [0035] Clarify matrix descriptor bounds checking granularity Aug 27, 2026
@damyanp
Damyan Pepper (damyanp) merged commit 4df2bd5 into microsoft:main Aug 31, 2026
6 checks passed
@github-project-automation github-project-automation Bot moved this to Triaged in HLSL Triage Aug 31, 2026
@damyanp
Damyan Pepper (damyanp) deleted the damyanp-matrix-bounds-checking branch August 31, 2026 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Triaged

Development

Successfully merging this pull request may close these issues.

2 participants