There is only one case where GVRequiresExtraLoad returns true for calls:

split its handling out to PCRelGVRequiresExtraLoad, and simplify code
based on this.

llvm-svn: 75230

1 files changed, 7 insertions, 1 deletions

diff --git a/llvm/lib/Target/X86/X86Subtarget.h b/llvm/lib/Target/X86/X86Subtarget.h
index db3b5d5eaf9..b2e518ed39f 100644
--- a/llvm/lib/Target/X86/X86Subtarget.h
+++ b/llvm/lib/Target/X86/X86Subtarget.h
@@ -204,10 +204,16 @@ public:
   bool GVRequiresExtraLoad(const GlobalValue* GV, const TargetMachine &TM,
                            bool isDirectCall) const;
 
+  /// PCRelGVRequiresExtraLoad - True if accessing the GV from a PC-relative
+  /// operand like a call target requires an extra load.
+  bool PCRelGVRequiresExtraLoad(const GlobalValue *GV,
+                                const TargetMachine &TM) const;
+  
+  
   /// True if accessing the GV requires a register.  This is a superset of the
   /// cases where GVRequiresExtraLoad is true.  Some variations of PIC require
   /// a register, but not an extra load.
-  bool GVRequiresRegister(const GlobalValue* GV, const TargetMachine &TM) const;
+  bool GVRequiresRegister(const GlobalValue *GV, const TargetMachine &TM) const;
 
   /// IsLegalToCallImmediateAddr - Return true if the subtarget allows calls
   /// to immediate address.