Skip to content

[DirectX] Max64UAVs shader flag analysis does not pass validation under all cases #139024

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.

Sign up for GitHub

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

Jump to bottom
Open
farzonl opened this issue May 8, 2025 · 0 comments
Open

[DirectX] Max64UAVs shader flag analysis does not pass validation under all cases #139024

farzonl opened this issue May 8, 2025 · 0 comments
Assignees
@Icohedron
Labels
backend:DirectX

Comments

@farzonl
Copy link
Member

farzonl commented May 8, 2025 •
edited by Icohedron
Loading

error: Flags must match usage.
66 cases

There are three cases:

  1. Flags declared=524336, actual=557104
    32 cases
  2. Flags declared=0, actual=32768
    20 cases
  3. Flags declared=48, actual=32816
    14 cases

All three cases are caused by bit 0x8000 not being set when it should be set.
This bit corresponds to the Max64UAVs (64 UAV slots) shader flag.
@Icohedron Icohedron self-assigned this May 8, 2025
@Icohedron Icohedron moved this to Planning in HLSL Support May 8, 2025
@Icohedron Icohedron changed the title [DirectX] Validator is complaining about Flags must match usage. [DirectX] Max64UAVs shader flag analysis does not pass validation under all cases May 12, 2025
@damyanp damyanp moved this from Planning to Active in HLSL Support May 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Icohedron Icohedron

Labels
backend:DirectX
Projects
HLSL Support
Status: Active
Milestone
No milestone
Development

No branches or pull requests
2 participants
@farzonl @Icohedron