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 09160a98218e7f1038e06c5d8e704a826ed0ae13
5a2ea20833f698fab9d14d818621b8ec0a74333b --extensions cpp --
clang/lib/CodeGen/CGCall.cpp clang/lib/CodeGen/CGExpr.cpp
``````````
</details>
<details>
<summary>
View the diff from clang-format here.
</summary>
``````````diff
diff --git a/clang/lib/CodeGen/CGExpr.cpp b/clang/lib/CodeGen/CGExpr.cpp
index 1e2e321a31..0a1f611fa6 100644
--- a/clang/lib/CodeGen/CGExpr.cpp
+++ b/clang/lib/CodeGen/CGExpr.cpp
@@ -110,8 +110,8 @@ RawAddress CodeGenFunction::CreateTempAlloca(llvm::Type
*Ty, CharUnits Align,
llvm::Value *V = Alloca.getPointer();
assert((!getLangOpts().OpenCL ||
CGM.getTarget().getTargetAddressSpace(getASTAllocaAddressSpace()) ==
- CGM.getTarget().getTargetAddressSpace(LangAS::opencl_private)) &&
- "For OpenCL allocas must allocate in the private address space!");
+ CGM.getTarget().getTargetAddressSpace(LangAS::opencl_private)) &&
+ "For OpenCL allocas must allocate in the private address space!");
// Alloca always returns a pointer in alloca address space, which may
// be different from the type defined by the language. For example,
// in C++ the auto variables are in the default address space. Therefore
``````````
</details>
https://github.com/llvm/llvm-project/pull/113930
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
