[Mlir-commits] [mlir] [mlir][SPIRV] Add named-barrier type and OpNamedBarrierInitialize / OpMemoryNamedBarrier (PR #195664)
Erick Ochoa Lopez
llvmlistbot at llvm.org
Mon May 4 08:21:05 PDT 2026
================
@@ -1502,6 +1502,20 @@ LogicalResult spirv::MemoryBarrierOp::verify() {
return verifyMemorySemantics(getOperation(), getMemorySemantics());
}
+//===----------------------------------------------------------------------===//
+// spirv.MemoryNamedBarrierOp
+//===----------------------------------------------------------------------===//
+
+LogicalResult spirv::MemoryNamedBarrierOp::verify() {
+ return verifyMemorySemantics(getOperation(), getMemorySemantics());
+}
+
+//===----------------------------------------------------------------------===//
+// spirv.NamedBarrierInitializeOp
+//===----------------------------------------------------------------------===//
+
+LogicalResult spirv::NamedBarrierInitializeOp::verify() { return success(); }
----------------
amd-eochoalo wrote:
Do we need this verification if it is just `success`? (I see that this is not the only one with `success` as verification, so I assume it is needed by the base class and it is ok.)
https://github.com/llvm/llvm-project/pull/195664
More information about the Mlir-commits
mailing list