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 55c9f24344a49cd1deb86af1d79d4dc3a798c6fb
5e35c30414517b242a1e68d46ecc5cfae3b75130 --
clang/test/Driver/bounds-safety-unused.c clang/test/Driver/fbounds-safety.c
clang/test/Frontend/bounds-safety-lang-support.c
clang/lib/Driver/ToolChains/Clang.cpp clang/lib/Frontend/CompilerInvocation.cpp
``````````
</details>
<details>
<summary>
View the diff from clang-format here.
</summary>
``````````diff
diff --git a/clang/lib/Frontend/CompilerInvocation.cpp
b/clang/lib/Frontend/CompilerInvocation.cpp
index 775fb4434cd5..17946ca8a2e2 100644
--- a/clang/lib/Frontend/CompilerInvocation.cpp
+++ b/clang/lib/Frontend/CompilerInvocation.cpp
@@ -3623,7 +3623,7 @@ static void CheckBoundsSafetyLang(InputKind IK,
DiagnosticsEngine &Diags) {
// possible to pass assembly files and LLVM IR through Clang, and
// those should be trivially supported. This is especially important because
// some build systems, like xcbuild and somewhat clumsy Makefiles, will pass
- // C_FLAGS to Clang while building assembly files.
+ // C_FLAGS to Clang while building assembly files.
switch (IK.getLanguage()) {
case Language::Unknown:
case Language::LLVM_IR:
``````````
</details>
https://github.com/llvm/llvm-project/pull/70480
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
