[PATCH] D22356: [ThinLTO] Perform conservative weak/linkonce resolution in distributed backend case

[Mehdi Amini via llvm-commits]

> On Jul 19, 2016, at 6:12 AM, Teresa Johnson <tejohnson at google.com> wrote:
> 
> 
> 
> On Mon, Jul 18, 2016 at 10:40 PM, Xinliang David Li <davidxl at google.com <mailto:davidxl at google.com>> wrote:
> Good example.  I think I am convinced :)
> 
> Yes, I can't think of another way to get this case to work without being far more conservative about importing, unfortunately. Ok, let me figure out what the best way is to transmit this info on to the final link through the build system. Probably through a file that can be directly used with the @ linker option in place of input files.

Do you have an example where it matters?
The only case I can imagine is mixing ThinLTO files with non-ThinLTO files, and the same weak symbol defined in both.

— 
Mehdi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20160719/e3df2ee2/attachment.html>