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.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@92995 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Eric Christopher 2010-01-08 08:24:49 +00:00
parent 6f279e0bda
commit 968b35ff47

View File

@ -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);