[LLVMdev] Problems with lazy linking change

[Rafael Ávila de Espíndola]

On 11/04/2011 01:46 PM, Matt Pharr wrote:
> r143524 changed ModuleLinker such that when linking a Module B into a
> Module A, any internal/private/... functions in B are only linked
> into A if there is a use of them in A.  This is problematic for my
> usage of module linking, where I'm basically linking a few modules
> together (some of which include internal functions) and then
> generating additional code that may use some of the internal
> functions--so I'd like everything to be linked in at the start, so
> that all of those functions are available.  I don't want to not mark
> those functions as internal, since if they're not used, I'd like them
> to be eliminated when I'm done with compilation.  With this change,
> those functions are now no longer available.
> 

This is an interesting regression that also affects LTO. I have reported
llvm.org/pr11367 for tracking it.

Thanks for finding it!

> Thanks, -matt

Cheers,
Rafael