diff options
| author | Jason Ekstrand <[email protected]> | 2017-09-01 09:59:34 -0700 |
|---|---|---|
| committer | Jason Ekstrand <[email protected]> | 2017-11-07 10:37:52 -0800 |
| commit | 7a82ad54bb56cafaeea7f909cd9fc35542c23ba0 (patch) | |
| tree | 952c45b655a7626356a563a6dcb71b65cd0a98d0 /src/intel/compiler/brw_eu.c | |
| parent | 6132992cdb858268af0e985727d80e4140be389c (diff) | |
intel/fs: Rework zero-length URB write handling
Originally we tried to handle this case based on slots_valid. However,
there are a number of ways that this can go wrong. For one, we throw
away any trailing slots which either aren't written or are set to
VARYING_SLOT_PAD. Second, even if PSIZ is a valid slot, we may not
actually write anything there. Between the lot of these, it was
possible to end up in a case where we tried to do a regular URB write
but ended up with a length of 1 which is invalid. This commit moves it
to the end and makes it based on a new boolean flag urb_written.
Reviewed-by: Iago Toral Quiroga <[email protected]>
Cc: [email protected]
Diffstat (limited to 'src/intel/compiler/brw_eu.c')
0 files changed, 0 insertions, 0 deletions