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 c,h,cpp -- 
clang/test/CodeGen/attr-flatten-deep-cg.c clang/test/Sema/attr-flatten-deep.c 
clang/lib/CodeGen/CodeGenModule.cpp clang/lib/Sema/SemaDeclAttr.cpp 
llvm/include/llvm/AsmParser/LLParser.h llvm/include/llvm/Bitcode/LLVMBitCodes.h 
llvm/include/llvm/IR/Attributes.h llvm/lib/AsmParser/LLParser.cpp 
llvm/lib/Bitcode/Reader/BitcodeReader.cpp 
llvm/lib/Bitcode/Writer/BitcodeWriter.cpp llvm/lib/IR/Attributes.cpp 
llvm/lib/Transforms/Utils/CodeExtractor.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/llvm/lib/AsmParser/LLParser.cpp b/llvm/lib/AsmParser/LLParser.cpp
index 1390d46dc..7265f2f1d 100644
--- a/llvm/lib/AsmParser/LLParser.cpp
+++ b/llvm/lib/AsmParser/LLParser.cpp
@@ -1625,8 +1625,7 @@ bool LLParser::parseEnumAttribute(Attribute::AttrKind 
Attr, AttrBuilder &B,
     if (InAttrGroup) {
       Lex.Lex();
       LocTy DepthLoc = Lex.getLoc();
-      if (parseToken(lltok::equal, "expected '=' here") ||
-          parseUInt64(Depth))
+      if (parseToken(lltok::equal, "expected '=' here") || parseUInt64(Depth))
         return true;
       if (!Depth)
         return error(DepthLoc, "flatten_deep depth must be non-zero");

``````````

</details>


https://github.com/llvm/llvm-project/pull/165777
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to