Descriptioncommand_buffer: Make inactive bound fragment inputs reserve the location
Specifying fragment input values with locations bound with
CHROMIUM_path_rendering should work, regardless whether the underlying
driver optimized the variable away or not.
Fixes the case where updating an inactive fragment input would cause
INVALID_OPERATION, because the location was empty.
Fixes the case where updating an fragment input would cause wrong
fragment input to be updated, if the fragment input was inactive and
bound to a location that would be assigned to an unbound fragment input.
Makes the Program::fragment_input_infos_ array linear (non-sparse). The
location bindings are now handled with
Program::fragment_input_locations_ sparse array.
BUG=542355
Committed: https://crrev.com/32956ea104eb269f7dd4c7a00d05d9663f538fa8
Cr-Commit-Position: refs/heads/master@{#361266}
Patch Set 1 #
Total comments: 4
Patch Set 2 : rebase #
Messages
Total messages: 14 (5 generated)
|