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 42096a48034185afe411226ca268b2796d1f9faa
7b2af0e256ed54102a3be69d62ff21cbccfa4e6d --extensions cpp,h --
llvm/include/llvm/CodeGen/RegUsageInfoCollector.h
llvm/include/llvm/CodeGen/RegisterUsageInfo.h
llvm/include/llvm/InitializePasses.h
llvm/include/llvm/Passes/CodeGenPassBuilder.h llvm/lib/CodeGen/CodeGen.cpp
llvm/lib/CodeGen/RegUsageInfoCollector.cpp
llvm/lib/CodeGen/RegisterUsageInfo.cpp llvm/lib/Passes/PassBuilder.cpp
``````````
</details>
<details>
<summary>
View the diff from clang-format here.
</summary>
``````````diff
diff --git a/llvm/lib/CodeGen/RegUsageInfoCollector.cpp
b/llvm/lib/CodeGen/RegUsageInfoCollector.cpp
index 0457c1f319..4f5c7f6efe 100644
--- a/llvm/lib/CodeGen/RegUsageInfoCollector.cpp
+++ b/llvm/lib/CodeGen/RegUsageInfoCollector.cpp
@@ -126,9 +126,10 @@ bool RegUsageInfoCollector::run(MachineFunction &MF) {
const TargetRegisterInfo *TRI = MF.getSubtarget().getRegisterInfo();
const LLVMTargetMachine &TM = MF.getTarget();
- LLVM_DEBUG(dbgs() << " -------------------- Register Usage Information
Collector Pass"
- << " -------------------- \nFunction Name : "
- << MF.getName() << '\n');
+ LLVM_DEBUG(
+ dbgs()
+ << " -------------------- Register Usage Information Collector Pass"
+ << " -------------------- \nFunction Name : " << MF.getName() << '\n');
// Analyzing the register usage may be expensive on some targets.
if (!isCallableFunction(MF)) {
``````````
</details>
https://github.com/llvm/llvm-project/pull/113874
_______________________________________________
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
