From 69d74739fd05b373453afe5864a14ff49cb67dd8 Mon Sep 17 00:00:00 2001
From: Ian Romanick <ian.d.romanick@intel.com>
Date: Fri, 15 Nov 2024 11:39:42 -0800
Subject: [PATCH] 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>
---
 src/intel/compiler/brw_fs_opt_algebraic.cpp | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/src/intel/compiler/brw_fs_opt_algebraic.cpp b/src/intel/compiler/brw_fs_opt_algebraic.cpp
index 7ac956d36b2..9b8ed770e3a 100644
--- a/src/intel/compiler/brw_fs_opt_algebraic.cpp
+++ b/src/intel/compiler/brw_fs_opt_algebraic.cpp
@@ -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];