e2b896aa64
This patch add support of intrinsics Fortran 2008 EXECUTE_COMMAND_LINE. The patch contains both the lowering and the runtime code and works on both Windows and Linux. The patch contains a list of commits, to convey the authorship and the history of changes. Some implementation specifics or status has been added to `flang/docs/Intrinsics.md`. I have provided a summary of the usage and the options required for the `EXECUTE_COMMAND_LINE intrinsic`. The intrinsic supports both a synchronous (by default) and an asynchronous option. | System | Mode | Implemention | |---------|-------|---------------------------| | Linux | Sync | std::system() | | Windows | Sync | std::system() | | Linux | Async | fork() | | Windows | Async | CreateProcess | Support for the SYSTEM GNU extension will be added in a separate PR. Co-authored with @jeffhammond --------- Signed-off-by: Jeff Hammond <jeff.science@gmail.com> Co-authored-by: Jeff Hammond <jeff.science@gmail.com> Co-authored-by: Yi Wu <yiwu02@wdev-yiwu02.arm.com>
45 lines
2.2 KiB
C++
45 lines
2.2 KiB
C++
//===-- Execute.cpp -- generate command line runtime API calls ------------===//
|
|
//
|
|
// 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
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#include "flang/Optimizer/Builder/Runtime/Execute.h"
|
|
#include "flang/Optimizer/Builder/FIRBuilder.h"
|
|
#include "flang/Optimizer/Builder/Runtime/RTBuilder.h"
|
|
#include "flang/Runtime/execute.h"
|
|
|
|
using namespace Fortran::runtime;
|
|
|
|
// Certain runtime intrinsics should only be run when select parameters of the
|
|
// intrisic are supplied. In certain cases one of these parameters may not be
|
|
// given, however the intrinsic needs to be run due to another required
|
|
// parameter being supplied. In this case the missing parameter is assigned to
|
|
// have an "absent" value. This typically happens in IntrinsicCall.cpp. For this
|
|
// reason the extra indirection with `isAbsent` is needed for testing whether a
|
|
// given parameter is actually present (so that parameters with "value" absent
|
|
// are not considered as present).
|
|
inline bool isAbsent(mlir::Value val) {
|
|
return mlir::isa_and_nonnull<fir::AbsentOp>(val.getDefiningOp());
|
|
}
|
|
|
|
void fir::runtime::genExecuteCommandLine(fir::FirOpBuilder &builder,
|
|
mlir::Location loc,
|
|
mlir::Value command, mlir::Value wait,
|
|
mlir::Value exitstat,
|
|
mlir::Value cmdstat,
|
|
mlir::Value cmdmsg) {
|
|
auto runtimeFunc =
|
|
fir::runtime::getRuntimeFunc<mkRTKey(ExecuteCommandLine)>(loc, builder);
|
|
mlir::FunctionType runtimeFuncTy = runtimeFunc.getFunctionType();
|
|
mlir::Value sourceFile = fir::factory::locationToFilename(builder, loc);
|
|
mlir::Value sourceLine =
|
|
fir::factory::locationToLineNo(builder, loc, runtimeFuncTy.getInput(6));
|
|
llvm::SmallVector<mlir::Value> args = fir::runtime::createArguments(
|
|
builder, loc, runtimeFuncTy, command, wait, exitstat, cmdstat, cmdmsg,
|
|
sourceFile, sourceLine);
|
|
builder.create<fir::CallOp>(loc, runtimeFunc, args);
|
|
}
|