[llvm-dev] RFC [ThinLTO]: Promoting more aggressively in order to reduce incremental link time and allow sharing between linkage units

[Peter Collingbourne via llvm-dev]

On Thu, Apr 7, 2016 at 11:42 AM, Rafael Espíndola <
rafael.espindola at gmail.com> wrote:

> > I imagine that for some linkers, it may not be possible to deal with this
> > scheme. For example, I did some investigation last year and discovered
> that
> > I could not use the gold plugin interface to load a native object file
> if we
> > had already claimed it as an IR file. I wouldn't be surprised to learn
> that
> > ld64 has similar problems.
>
> Can't you just call add_input_file with the original file in addition
> to any .o files you created during linking?
>

I think that almost worked, but I kept running into issues relating to the
fact that the plugin needed to inform the linker about symbols in the
native object file via add_symbols. What I ended up with was kind of
unsound and still didn't work correctly for (at least) some parts of
Chromium.

I suppose I can try to pull up that work again and go into more detail on
what exactly the issues were, if you're interested.

-- 
-- 
Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160407/413fcf9d/attachment.html>