From ebc2c71d63b69d90aadf07968f821267442f56ef Mon Sep 17 00:00:00 2001 From: Andrzej Warzynski Date: Fri, 21 Jul 2023 10:47:36 +0100 Subject: [flang][nfc] Clarify the usage of llvmArgs and mlirArgs Differential Revision: https://reviews.llvm.org/D155931 --- flang/lib/Frontend/CompilerInvocation.cpp | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'flang/lib/Frontend/CompilerInvocation.cpp') diff --git a/flang/lib/Frontend/CompilerInvocation.cpp b/flang/lib/Frontend/CompilerInvocation.cpp index 43fecca..b1f0d27 100644 --- a/flang/lib/Frontend/CompilerInvocation.cpp +++ b/flang/lib/Frontend/CompilerInvocation.cpp @@ -950,9 +950,14 @@ bool CompilerInvocation::createFromArgs( success &= parseSemaArgs(res, args, diags); success &= parseDialectArgs(res, args, diags); success &= parseDiagArgs(res, args, diags); + + // Collect LLVM (-mllvm) and MLIR (-mmlir) options. + // NOTE: Try to avoid adding any options directly to `llvmArgs` or + // `mlirArgs`. Instead, you can use + // * `-mllvm `, or + // * `-mmlir `. res.frontendOpts.llvmArgs = args.getAllArgValues(clang::driver::options::OPT_mllvm); - res.frontendOpts.mlirArgs = args.getAllArgValues(clang::driver::options::OPT_mmlir); -- cgit v1.1