github-actions[bot] wrote:
<!--LLVM CODE FORMAT COMMENT: {clang-format}-->
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
<details>
<summary>
You can test this locally with the following command:
</summary>
``````````bash
git-clang-format --diff origin/main HEAD --extensions cpp --
clang/lib/CIR/CodeGen/CIRGenCUDANV.cpp
clang/lib/CIR/Dialect/Transforms/LoweringPrepare.cpp --diff_from_common_commit
``````````
:warning:
The reproduction instructions above might return results for more than one PR
in a stack if you are using a stacked PR workflow. You can limit the results by
changing `origin/main` to the base branch/commit you want to compare against.
:warning:
</details>
<details>
<summary>
View the diff from clang-format here.
</summary>
``````````diff
diff --git a/clang/lib/CIR/CodeGen/CIRGenCUDANV.cpp
b/clang/lib/CIR/CodeGen/CIRGenCUDANV.cpp
index 1c6d04916..7be04dbda 100644
--- a/clang/lib/CIR/CodeGen/CIRGenCUDANV.cpp
+++ b/clang/lib/CIR/CodeGen/CIRGenCUDANV.cpp
@@ -524,8 +524,9 @@ void CIRGenNVCUDARuntime::handleGlobalReplace(cir::GlobalOp
oldGV,
}
/// Whether this translation unit has anything for the CUDA runtime to
register.
-/// Like LoweringPrepare, count only kernel stub definitions and device
variables
-/// carrying registration metadata, not kernel declarations or launch-site
calls.
+/// Like LoweringPrepare, count only kernel stub definitions and device
+/// variables carrying registration metadata, not kernel declarations or
+/// launch-site calls.
static bool hasEntitiesToRegister(mlir::ModuleOp module) {
// A walk, not a scan of the module body, so this stays in agreement with the
// recursive walk LoweringPrepare collects them with.
``````````
</details>
https://github.com/llvm/llvm-project/pull/231390
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
