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 h,cpp --
lldb/include/lldb/Utility/ArchSpec.h lldb/source/Utility/ArchSpec.cpp
llvm/include/llvm/Object/ELFObjectFile.h
llvm/include/llvm/TargetParser/Triple.h llvm/lib/Object/ELFObjectFile.cpp
llvm/lib/Object/ObjectFile.cpp llvm/lib/TargetParser/TargetDataLayout.cpp
llvm/lib/TargetParser/Triple.cpp llvm/unittests/Object/ELFObjectFileTest.cpp
``````````
: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/TargetParser/Triple.cpp b/llvm/lib/TargetParser/Triple.cpp
index ac3626db4..72e9cb9f4 100644
--- a/llvm/lib/TargetParser/Triple.cpp
+++ b/llvm/lib/TargetParser/Triple.cpp
@@ -53,7 +53,8 @@ StringRef Triple::getArchTypeName(ArchType Kind) {
case mipsel: return "mipsel";
case msp430: return "msp430";
case nvptx64: return "nvptx64";
- case nvptx: return "nvptx";
+ case nvptx:
+ return "nvptx";
case ppc64: return "powerpc64";
case ppc64le: return "powerpc64le";
case ppc: return "powerpc";
``````````
</details>
https://github.com/llvm/llvm-project/pull/159879
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
