intel/fs: Add need_dest parameter to fs_visitor::nir_emit_alu
authorIan Romanick <ian.d.romanick@intel.com>
Tue, 21 May 2019 19:09:42 +0000 (12:09 -0700)
committerIan Romanick <ian.d.romanick@intel.com>
Thu, 6 Jun 2019 00:04:08 +0000 (17:04 -0700)
commita288708506d2206945d13ccf6b2abb80f2a6305b
tree209566a7ae6f1e59cb0812d561bcbd58ce3bb0aa
parente13a5c7d676021b2d1030e3644db95eb1803e767
intel/fs: Add need_dest parameter to fs_visitor::nir_emit_alu

This is the same as the need_dest parameter to
prepare_alu_destination_and_sources.  This allows us to not change the
register that is expected to hold an result if an instruction is
re-emitted.  This is particularly a problem if the re-emitted
instruction is a partial write.  A later patch will use this feature.

No shader-db changes on any Intel platform.

v2: Don't do the Boolean resolve when there is no destination.  If the
ALU instruction didn't write a register, there's nothing to resolve.
This replaces an earlier patch "intel/fs: Allocate dummy destination
register when need_dest is false".

Reviewed-by: Caio Marcelo de Oliveira Filho <caio.oliveira@intel.com>
Reviewed-by: Matt Turner <mattst88@gmail.com>
src/intel/compiler/brw_fs.h
src/intel/compiler/brw_fs_nir.cpp