From: Chad Rosier <mcrosier@codeaurora.org>
Date: Fri, 11 Nov 2016 19:52:45 +0000 (+0000)
Subject: [AArch64] Update a FIXME comment to reflect current state. NFC.
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ed7a0c4856116aed3d5ecb7876940bfed4cf83ef;p=llvm

[AArch64] Update a FIXME comment to reflect current state. NFC.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@286625 91177308-0d34-0410-b5e6-96231b3b80d8
---

diff --git a/lib/Target/AArch64/AArch64LoadStoreOptimizer.cpp b/lib/Target/AArch64/AArch64LoadStoreOptimizer.cpp
index fc5ed6e9c8c..7aed5d65600 100644
--- a/lib/Target/AArch64/AArch64LoadStoreOptimizer.cpp
+++ b/lib/Target/AArch64/AArch64LoadStoreOptimizer.cpp
@@ -1706,8 +1706,10 @@ bool AArch64LoadStoreOpt::runOnMachineFunction(MachineFunction &Fn) {
   return Modified;
 }
 
-// FIXME: Do we need/want a pre-alloc pass like ARM has to try to keep
-// loads and stores near one another?
+// FIXME: Do we need/want a pre-alloc pass like ARM has to try to keep loads and
+// stores near one another?  Note: The pre-RA instruction scheduler already has
+// hooks to try and schedule pairable loads/stores together to improve pairing
+// opportunities.  Thus, pre-RA pairing pass may not be worth the effort.
 
 // FIXME: When pairing store instructions it's very possible for this pass to
 // hoist a store with a KILL marker above another use (without a KILL marker).