[Mlir-commits] [mlir] [mlir][arith] Use type parser instead of hard-coding type keywords (PR #186753)

[Matthias Springer]

================
@@ -1,4 +1,9 @@
-// RUN: mlir-opt --split-input-file --arith-emulate-unsupported-floats="source-types=bf16,f8E4M3FNUZ target-type=f32" %s | FileCheck %s
+// RUN: mlir-opt --arith-emulate-unsupported-floats="source-types=bf16,f8E4M3FNUZ target-type=f32" %s | FileCheck %s
+// RUN: mlir-opt --arith-emulate-unsupported-floats="source-types=bf16,f8E4M3FNUZ target-type=!llvm.ppc_fp128" %s | FileCheck %s --check-prefix=CHECK-PPC
+
+// Arbitrary op from the LLVM dialect to ensure that the LLVM dialect is loaded.
+// The LLVM dialect is needed for the !llvm.ppc_fp128 test run.
----------------
matthias-springer wrote:

Is there an API for that? I was trying to call this function in `getDependentDialects`, but I don't know the type ID:

```c++
  /// Add a new dialect constructor to the registry. The constructor must be
  /// calling MLIRContext::getOrLoadDialect in order for the context to take
  /// ownership of the dialect and for delayed interface registration to happen.
  void insert(TypeID typeID, StringRef name,
              const DialectAllocatorFunction &ctor);
```


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