maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

[mlir] AsynToLLVM: do no use op->getOperands() in conversion patterns 

Differential Revision: https://reviews.llvm.org/D91910
This commit is contained in:
Eugene Zhulenev 2020-11-21 03:50:05 -08:00
parent d4f1a3c6e2
commit 13ab072b25
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
mlir/lib/Conversion/AsyncToLLVM/AsyncToLLVM.cpp
View File

@ -592,7 +592,7 @@ public:
CallOp call = cast<CallOp>(op);
rewriter.replaceOpWithNewOp<CallOp>(op, resultTypes, call.callee(),
call.getOperands());
operands);
return success();
}
@ -733,7 +733,7 @@ public:
// async API await function call.
if (!isInCoroutine)
rewriter.create<CallOp>(loc, TypeRange(), blockingAwaitFuncName,
ValueRange(op->getOperand(0)));
ValueRange(operands[0]));
// Inside the coroutine we convert await operation into coroutine suspension
// point, and resume execution asynchronously.
@ -755,8 +755,8 @@ public:
// Call async runtime API to resume a coroutine in the managed thread when
// the async await argument becomes ready.
SmallVector<Value, 3> awaitAndExecuteArgs = {
await.getOperand(), coro.coroHandle, resumePtr.res()};
SmallVector<Value, 3> awaitAndExecuteArgs = {operands[0], coro.coroHandle,
resumePtr.res()};
builder.create<CallOp>(loc, TypeRange(), coroAwaitFuncName,
awaitAndExecuteArgs);