[llvm] [AArch64][SME] Fix ADDVL addressing to scavenged stackslot. (PR #109674)

via llvm-commits llvm-commits at lists.llvm.org
Mon Sep 23 08:19:24 PDT 2024


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 3c83102f0615c7d66f6df698ca472ddbf0e9483d 0e279fde3ac52457650fbe46fb03098f007cc727 --extensions cpp -- llvm/lib/Target/AArch64/AArch64FrameLowering.cpp
``````````

</details>

<details>
<summary>
View the diff from clang-format here.
</summary>

``````````diff
diff --git a/llvm/lib/Target/AArch64/AArch64FrameLowering.cpp b/llvm/lib/Target/AArch64/AArch64FrameLowering.cpp
index 30c3a886c4..9a2774e206 100644
--- a/llvm/lib/Target/AArch64/AArch64FrameLowering.cpp
+++ b/llvm/lib/Target/AArch64/AArch64FrameLowering.cpp
@@ -2761,7 +2761,8 @@ StackOffset AArch64FrameLowering::resolveFrameOffsetReference(
         // If the FPOffset is positive, that'll always be best, as the SP/BP
         // will be even further away.
         UseFP = true;
-      } if (MFI.hasVarSizedObjects()) {
+      }
+      if (MFI.hasVarSizedObjects()) {
         // If we have variable sized objects, we can use either FP or BP, as the
         // SP offset is unknown. We can use the base pointer if we have one and
         // FP is not preferred. If not, we're stuck with using FP.

``````````

</details>


https://github.com/llvm/llvm-project/pull/109674


More information about the llvm-commits mailing list