i965/nir: Use nir_op_info.output_type for determining when to resolve
authorJason Ekstrand <jason.ekstrand@intel.com>
Mon, 3 Aug 2015 21:12:35 +0000 (14:12 -0700)
committerJason Ekstrand <jason.ekstrand@intel.com>
Mon, 10 Aug 2015 18:45:43 +0000 (11:45 -0700)
commit17c978166185a7d3a9759f828a4370c1f2169776
treeaf225423632ed645b5d9fba4e8f7cbd3676495dd
parent9901aeb1c74648cbe1aa1d18d590a689c844cbad
i965/nir: Use nir_op_info.output_type for determining when to resolve

Previously, we were explicitly listing every instruction that needs a
resolve.  However, those instructions were precicely the ones that returned
booleans so there's no reason why we shouldn't just have that check.  Also,
all of the reduction opcodes such as bany and ball were missing so it
didn't properly flag stuff on vec4.  If an opcode gets added in the future
that returns a bool but doesn't need a resolve, we can special-case that.

Reviewed-by: Matt Turner <mattst88@gmail.com>
src/mesa/drivers/dri/i965/brw_nir_analyze_boolean_resolves.c