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/Analysis/UnsafeBufferUsage.cpp
clang/test/SemaCXX/warn-unsafe-buffer-usage-libc-functions.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/Analysis/UnsafeBufferUsage.cpp
b/clang/lib/Analysis/UnsafeBufferUsage.cpp
index 0d0bfdd0f..4d35dec3c 100644
--- a/clang/lib/Analysis/UnsafeBufferUsage.cpp
+++ b/clang/lib/Analysis/UnsafeBufferUsage.cpp
@@ -1161,8 +1161,8 @@ static bool isUnsafeMemset(const CallExpr &Node,
ASTContext &Ctx) {
// Now we have a real call to memset, it's considered unsafe unless it's in
// the form `memset(&x, 0, sizeof(x))`.
- const auto *AddressOfVar =
-
dyn_cast_if_present<DeclRefExpr>(getSubExprInAddressOfExpr(Node.getArg(0)));
+ const auto *AddressOfVar = dyn_cast_if_present<DeclRefExpr>(
+ getSubExprInAddressOfExpr(Node.getArg(0)));
if (!AddressOfVar)
return true;
``````````
</details>
https://github.com/llvm/llvm-project/pull/178107
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
