vkd3d-shader/hlsl: Parse rasteriser-ordered view types.
Merge request reports
Activity
requested review from @hverbeet
Modifiers are otherwise for actual modifier keywords. I can't say this is wrong but it's definitely weird. Less weird would be to use a dedicated HLSL_TYPE_* or a UAV-specific flag.
Something like
if (uav && resource->data_type->e.uav.rasteriser_ordered) instr.opcode |= VKD3DSUF_RASTERISER_ORDERED_VIEW << VKD3D_SM5_UAV_FLAGS_SHIFT;
you mean?
added 8 commits
-
03db60c8...e3ed5ac7 - 7 commits from branch
wine:master
- ee867bd4 - vkd3d-shader/hlsl: Parse rasteriser-ordered view types.
-
03db60c8...e3ed5ac7 - 7 commits from branch
How about the attached series? I turns out that it's a bit awkward to make the "rasteriser_ordered" flag specific to UAVs due to the way "resource_format" is currently used, but making it a resource flag seems close enough to me. The series has a minor conflict with 569.
How about the attached series? I turns out that it's a bit awkward to make the "rasteriser_ordered" flag specific to UAVs due to the way "resource_format" is currently used, but making it a resource flag seems close enough to me. The series has a minor conflict with 569. That also looks good to me.