[CPU] Enable fast min/max ops in CPU codegen (#15130)

This patch introduces a flag to generate `arith.minf/maxf` instead of `arith.minimumf/maximumf` ops in the CPU pipeline. We should enable the flag by default in the future as no ML compiler/library is actually caring about NaNs and +/-0.0 values by default.

compiler/src/iree/compiler/Codegen/LLVMCPU/Passes.cpp

diff --git a/compiler/src/iree/compiler/Codegen/LLVMCPU/Passes.cpp b/compiler/src/iree/compiler/Codegen/LLVMCPU/Passes.cpp
index d442a19..4feb706 100644
--- a/compiler/src/iree/compiler/Codegen/LLVMCPU/Passes.cpp
+++ b/compiler/src/iree/compiler/Codegen/LLVMCPU/Passes.cpp
@@ -44,6 +44,12 @@
         "Runs the pass to check if all the Linalg ops are vectorized"),
     llvm::cl::init(false));
 
+static llvm::cl::opt<bool> clUseFastMinMaxOps(
+    "iree-llvmcpu-use-fast-min-max-ops",
+    llvm::cl::desc(
+        "Use `arith.minf/maxf` instead of `arith.minimumf/maximumf` ops"),
+    llvm::cl::init(false));
+
 // TODO(#10820): Delete the flag. This should be a nop pass to default pipeline
 // while tensor.pad op is lowered to fill + insert_slice before Codegen.
 // However, it causes regressions in terms of compilation time. Skip the passes
@@ -710,6 +716,11 @@
   passManager.addNestedPass<func::FuncOp>(
       createHoistStaticallyBoundAllocationsPass());
 
+  // Use `arith.minf/maxf` instead of `arith.minimumf/maximumf`.
+  if (clUseFastMinMaxOps) {
+    passManager.addNestedPass<func::FuncOp>(createReplaceSlowMinMaxOpsPass());
+  }
+
   // Resolve get_buffer_descriptor ops. All structural buffer manipulations
   // must conclude before this point.
   passManager.addNestedPass<func::FuncOp>(