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,h --
llvm/include/llvm/Analysis/IR2Vec.h llvm/lib/Analysis/IR2Vec.cpp
llvm/tools/llvm-ir2vec/lib/Utils.cpp llvm/tools/llvm-ir2vec/lib/Utils.h
llvm/tools/llvm-ir2vec/llvm-ir2vec.cpp llvm/unittests/Analysis/IR2VecTest.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/tools/llvm-ir2vec/llvm-ir2vec.cpp
b/llvm/tools/llvm-ir2vec/llvm-ir2vec.cpp
index 56a5183ad..e8d7d9b19 100644
--- a/llvm/tools/llvm-ir2vec/llvm-ir2vec.cpp
+++ b/llvm/tools/llvm-ir2vec/llvm-ir2vec.cpp
@@ -155,9 +155,10 @@ static Error processModule(Module &M, raw_ostream &OS) {
// Note: Requires --ir2vec-vocab-path option to be set
// and this value will be populated in the var VocabFile
if (VocabFile.empty()) {
- return createStringError(errc::invalid_argument,
- "IR2Vec vocabulary file path not specified; "
- "You may need to set it using
--ir2vec-vocab-path");
+ return createStringError(
+ errc::invalid_argument,
+ "IR2Vec vocabulary file path not specified; "
+ "You may need to set it using --ir2vec-vocab-path");
}
auto VocabStatus = Tool.initializeVocabulary(VocabFile);
assert(VocabStatus && "Failed to initialize IR2Vec vocabulary");
``````````
</details>
https://github.com/llvm/llvm-project/pull/177361
_______________________________________________
llvm-branch-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
