aboutsummaryrefslogtreecommitdiff
path: root/loader/loader.c
diff options
context:
space:
mode:
authorCourtney Goeltzenleuchter <courtney@LunarG.com>2015-09-21 17:19:25 -0600
committerCourtney Goeltzenleuchter <courtney@LunarG.com>2015-09-23 11:15:00 -0600
commitb127bd60f48402ee949511b0df88be034d0d94dd (patch)
tree8fbf96df1bff78bb7ff4d32fb0918d0690a4d25d /loader/loader.c
parentd6217bc20873a7d70537921e7cea9be5572bc34c (diff)
downloadusermoji-b127bd60f48402ee949511b0df88be034d0d94dd.tar.xz
bug-14365: add dynamic state to PSO
This commit covers phase 2 of the removal of dynamic state objects. Now, an application can include an array of VK_DYNAMIC_STATE_* values that tell the driver which PSO dynamic state elements to use. I.e. if VK_DYNAMIC_STATE_LINE_WIDTH was specified in the pDynamicState array then the ICD should use the lineWidth defined at PSO create time and ignore any set using vkCmdSetLineWidth. To accomplish that the driver will make a copy of the dynamic state specified in the PSO as well as a bitmask of the affected state. When vkCmdSet* is called, the driver will check if a PSO override is current and ignore the call if so. At PSO bind time the command buffer's dynamic state will be updated and the PSO override bitmask set so that any future vkCmdSet*'s will be appropriately ignored. TODO: Validation layer should probably indicate a warning if app tries to do vkCmdSet on state defined by the PSO.
Diffstat (limited to 'loader/loader.c')
0 files changed, 0 insertions, 0 deletions