[Mlir-commits] [mlir] [mlir][gpu] Support `minimumnumf` and `maximumnumf` in GPU dialect (PR #226903)

[Lewis Crawford]

================
@@ -0,0 +1,21 @@
+// RUN: mlir-opt --convert-gpu-to-nvvm %s | FileCheck %s
+
+gpu.module @kernels {
+  // CHECK-LABEL: llvm.func @minimum_number
+  // CHECK: llvm.intr.minimumnum
+  // CHECK: llvm.return
+  gpu.func @minimum_number(%arg0 : f32, %out : memref<f32>) kernel {
+    %result = gpu.all_reduce minimumnumf %arg0 uniform {} : (f32) -> f32
+    memref.store %result, %out[] : memref<f32>
+    gpu.return
+  }
+
+  // CHECK-LABEL: llvm.func @maximum_number
+  // CHECK: llvm.intr.maximumnum
+  // CHECK: llvm.return
+  gpu.func @maximum_number(%arg0 : f32, %out : memref<f32>) kernel {
----------------
LewisCrawford wrote:

If adding `subgroup_reduce` tests for `maximumnumf`, it would be nice to make them symmetrical with `maxnum` and `maximum` too (which might mean adding 3 sets of new tests here).

https://github.com/llvm/llvm-project/pull/226903