anv_cmd_buffer: Don't make the initial state dirty
authorNanley Chery <nanley.g.chery@intel.com>
Thu, 7 Apr 2016 09:47:28 +0000 (02:47 -0700)
committerNanley Chery <nanley.g.chery@intel.com>
Thu, 14 Apr 2016 00:52:24 +0000 (17:52 -0700)
commit88d1c19c9dfd6be1a374917f707e3c77089d7013
treecee57b8b7b657d6d8e90b01b5ba1c6b590413613
parent9fae6ee02659463259e9d7d90a2edf5261887503
anv_cmd_buffer: Don't make the initial state dirty

Avoid excessive state emission. Relevant state for an action command
will get set by the user:

From Chapter 5. Command Buffers,
 When a command buffer begins recording, all state in that command
 buffer is undefined.
 [...]
 Whenever the state of a command buffer is undefined, the application
 must set all relevant state on the command buffer before any state
 dependent commands such as draws and dispatches are recorded, otherwise
 the behavior of executing that command buffer is undefined.

Signed-off-by: Nanley Chery <nanley.g.chery@intel.com>
Reviewed-by: Kristian Høgsberg Kristensen <kristian.h.kristensen@intel.com>
src/intel/vulkan/anv_cmd_buffer.c