After further thought revert the patch to make fast-isel avoid

putting relocations into the constant pool - this isn't needed
for correctness and in the rare occasion it happens would pull
us out of fast isel for the block.

If fast-isel application startup time ever becomes an issue we
can add better support for these addresses instead of bailing.

llvm-svn: 92995

1 files changed, 0 insertions, 6 deletions

diff --git a/llvm/lib/Target/X86/X86FastISel.cpp b/llvm/lib/Target/X86/X86FastISel.cpp
index 2986ec2c31a..10fba2461ed 100644
--- a/llvm/lib/Target/X86/X86FastISel.cpp
+++ b/llvm/lib/Target/X86/X86FastISel.cpp
@@ -1652,12 +1652,6 @@ unsigned X86FastISel::TargetMaterializeConstant(Constant *C) {
     PICBase = X86::RIP;
   }
 
-  // If we've gotten here we need to make sure we don't have a constant
-  // that needs a relocation, because then we shouldn't put it into the
-  // constant pool.
-  if (C->getRelocationInfo() != Constant::NoRelocation)
-    return 0;
-  
   // Create the load from the constant pool.
   unsigned MCPOffset = MCP.getConstantPoolIndex(C, Align);
   unsigned ResultReg = createResultReg(RC);