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,h --
clang/lib/CIR/CodeGen/CIRGenBuiltin.cpp
clang/lib/CIR/CodeGen/CIRGenBuiltinNVPTX.cpp
clang/lib/CIR/CodeGen/CIRGenFunction.h --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/CIRGenBuiltin.cpp
b/clang/lib/CIR/CodeGen/CIRGenBuiltin.cpp
index 0af0195e6..d67134583 100644
--- a/clang/lib/CIR/CodeGen/CIRGenBuiltin.cpp
+++ b/clang/lib/CIR/CodeGen/CIRGenBuiltin.cpp
@@ -163,9 +163,11 @@ static Address checkAtomicAlignment(CIRGenFunction &cgf,
const CallExpr *e) {
/// Utility to insert an atomic instruction based on Intrinsic::ID
/// and the expression node.
-mlir::Value CIRGenFunction::makeBinaryAtomicValue(
- cir::AtomicFetchKind kind, const CallExpr *expr, mlir::Type
*originalArgType,
- mlir::Value *emittedArgValue, cir::MemOrder ordering) {
+mlir::Value CIRGenFunction::makeBinaryAtomicValue(cir::AtomicFetchKind kind,
+ const CallExpr *expr,
+ mlir::Type *originalArgType,
+ mlir::Value *emittedArgValue,
+ cir::MemOrder ordering) {
CIRGenFunction &cgf = *this;
QualType type = expr->getType();
``````````
</details>
https://github.com/llvm/llvm-project/pull/210534
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
