[PATCH] D73465: Add gpu::LaunchOp::addKernelArgument.
Alex Zinenko via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Mon Jan 27 13:38:56 PST 2020
ftynse added inline comments.
================
Comment at: mlir/include/mlir/Dialect/GPU/GPUOps.td:487
+ incovation of the `gpu.func`.
+ As `gpu.launch` does not return any values, it is expected that a
+ corresponding `gpu.return` also has no operands.
----------------
herhut wrote:
> ftynse wrote:
> > This says "gpu.launch" but the line above says "gpu.func". Let's use one everywhere and say the other is equivalent.
> But they are not. When used inside of a launch, it cannot have operands. I could maybe state that gpu.launch is considered equivalent to a void function? I found it surprising that launch now has a return (as opposed to the terminator). That moves it closer to a function where it should feel more like a loop. WDYT about adding the terminator op back or is that too many operations?
Then it's even more confusing than I thought. I'm fine with having a separate terminator for `launch`.
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D73465/new/
https://reviews.llvm.org/D73465
More information about the llvm-commits
mailing list