[Mlir-commits] [mlir] [mlir][DLTI] Introduce an operation interface for scoped DLTI queries (PR #222776)

[Mehdi Amini]

================
@@ -0,0 +1,53 @@
+//===- DLTIOpInterfaces.td - DLTI operation interfaces -----*- tablegen -*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
+//
+//===----------------------------------------------------------------------===//
+
+#ifndef MLIR_DIALECT_DLTI_DLTIOPINTERFACES
+#define MLIR_DIALECT_DLTI_DLTIOPINTERFACES
+
+include "mlir/Interfaces/DataLayoutInterfaces.td"
+
+def DLTIQueryOpInterface : OpInterface<"DLTIQueryOpInterface"> {
+  let cppNamespace = "::mlir";
+
+  let description = [{
+    Operation interface for scoped DLTI key-value associations.
+
+    Queries and updates operate on one key at a time. The default
+    implementations use the operation's inherent `dlti` attribute. An update
+    preserves other entries in a `#dlti.map`; setting a null value removes an
+    entry. Updating a non-map `dlti` attribute or using a null or empty string
+    key fails.
----------------
joker-eph wrote:

sure, I used a kDltiAttrName

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