vkd3d-shader/hlsl: Handle "unsigned int" type.
1 unresolved thread
1 unresolved thread
Signed-off-by: Nikolay Sivov nsivov@codeweavers.com
Merge request reports
Activity
Conceptually, I would expect that if "unsigned" is legal for any integer type then it should be a property of the type, not how it's specified. Practically speaking, since no integer types are defined through keywords (that we know of), it would only make a difference for vector or matrix types.
Surprisingly enough though d3dcompiler actually rejects those, though, so I guess TYPE_IDENTIFIER is correct here after all. It's surprising though and deserves a comment.
added 1 commit
- 4c1bd3f3 - vkd3d-shader/hlsl: Handle "unsigned int" type.
added 15 commits
-
4c1bd3f3...a64426ed - 14 commits from branch
wine:master
- b79cc050 - vkd3d-shader/hlsl: Handle "unsigned int" type.
-
4c1bd3f3...a64426ed - 14 commits from branch
added 12 commits
-
b79cc050...36c123c0 - 11 commits from branch
wine:master
- ea177a77 - vkd3d-shader/hlsl: Handle "unsigned int" type.
-
b79cc050...36c123c0 - 11 commits from branch
Please register or sign in to reply