intel/ir: Drop hard-coded correspondence between IR and HW opcodes.
authorFrancisco Jerez <currojerez@riseup.net>
Wed, 24 Jan 2018 03:38:45 +0000 (19:38 -0800)
committerFrancisco Jerez <currojerez@riseup.net>
Fri, 11 Oct 2019 19:24:16 +0000 (12:24 -0700)
commit1b570456caecac5371dec9383a50f4f9877d3a61
tree3f562327579e9983f7483f2e93d8977ed1751560
parent057902dcf8d287f0b110b03f67ae33d338a7497c
intel/ir: Drop hard-coded correspondence between IR and HW opcodes.

Having the IR opcodes locked to their hardware representation is risky
because it causes opcodes as different as BRC and IFF to compare equal
at the IR level (luckily the back-end only ever uses one opcode from
each group, right now), and it prevents us from supporting
instructions that change their hardware representation across
generations, which will become a problem on Gen12+ platforms.

Reviewed-by: Caio Marcelo de Oliveira Filho <caio.oliveira@intel.com>
Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
src/intel/compiler/brw_eu_defines.h
src/intel/compiler/brw_shader.cpp