[llvm] r209007 - Fix most of PR10367.

[Owen Anderson]

On May 17, 2014, at 9:03 PM, Nick Lewycky <nicholas at mxc.ca> wrote:

>> 
>> I don’t see why.  Your more restrictive representation is just going to
>> arbitrarily limit the ability of frontends and backends to achieve things
>> that your representation doesn’t realize are possible.  LLVM IR should
>> not be in the business of knowing what common object file formats
>> are capable of expressing.
> 
> On the contrary, that is precisely the plan (my plan). Why shouldn't it?

Because LLVM is not (just) a C compiler.  LLVM is used in lots of applications, particularly ones involving online compilation, that have no meaningful concept of a relocation, or have very different ideas of what the loader.  Baking in more of the static C compilation model penalizes such use cases.

—Owen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20140518/8f2917f7/attachment.html>