[llvm-commits] [PATCH] Make X86-64 in the Large model always emit 64-bit calls

[Eric Christopher]

> 
> I'm trying for no far-stubs at all. :) With a unique stub for each
> GlobalValue, the _stub_ can be more than 2GB away from the code using
> it. And without either a unique stub or a bunch of work distinguishing
> uses from address-of operations, &GV == address_of_GV() can be false.

After we took this offline I think I figured out what the problem is. We still had a point where we were trying to tell llvm that we wanted a small code model instead of large.

That said, there's still a problem:  what if someone really does want small code model? Do we want to support that? If so, then we need to have some way of making small code model continue to work on x86-64. I do have an internal customer that we believe needs small code model. Unless the new way has no disadvantages over small?

-eric

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: z.diff.txt
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20091115/89695d69/attachment.txt>