[Mlir-commits] [mlir] [mlir][gpu] Add field to mark asynchronous side effects (PR #72013)
Oleksandr Alex Zinenko
llvmlistbot at llvm.org
Mon Nov 13 04:24:03 PST 2023
================
@@ -183,6 +184,9 @@ class SideEffect<EffectOpInterfaceBase interface, string effectName,
// Does this side effect act on every single value of resource.
bit effectOnFullRegion = range.Value;
+
+ // Does this side effect potentially occur after op exit
+ bit asynchronous = isAsync;
----------------
ftynse wrote:
FYI, effect instances have an attribute field for additional qualification of effects. It may be worth using, rather than pushing `asynchronous` on every potential client, as long as one can come up with a "conservatively safe" way of handling side effects while ignoring this information.
https://github.com/llvm/llvm-project/pull/72013
More information about the Mlir-commits
mailing list