brw/algebraic: Don't restrict MAD(a, b, 1) optimization to float32

This is very unlikely for floating point MAD. At some point I intend
to add internal integer MAD uses, and this could occur there.

No shader-db or fossil-db changes on any Intel platform.

Reviewed-by: Caio Oliveira <caio.oliveira@intel.com>
Reviewed-by: Matt Turner <mattst88@gmail.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/32436>
This commit is contained in:
Ian Romanick 2024-11-15 11:39:42 -08:00 committed by Marge Bot
parent b605f76b2a
commit 69d74739fd

View file

@ -668,10 +668,6 @@ brw_fs_opt_algebraic(fs_visitor &s)
break;
}
if (inst->src[0].type != BRW_TYPE_F ||
inst->src[1].type != BRW_TYPE_F ||
inst->src[2].type != BRW_TYPE_F)
break;
if (inst->src[1].is_one()) {
inst->opcode = BRW_OPCODE_ADD;
inst->src[1] = inst->src[2];