[PATCH] D12226: [LLD] Support for --unresolved-symbols option in llvm lld for ELF file format

[shridHar joshi via llvm-commits]

> I'm not sure if the bfd or gold behavior is correct here, I can
> certainly think of situations where it is plainly wrong.

Please elaborate, probably with the specific use cases so that i can cross
check.

-Shridhar

On Mon, Sep 14, 2015 at 7:43 PM, Joerg Sonnenberger via llvm-commits <
llvm-commits at lists.llvm.org> wrote:

> On Mon, Sep 14, 2015 at 03:56:21PM +0530, shridHar joshi via llvm-commits
> wrote:
> > in case of gnu ld and gold, allow shlib undefined is false (default)
> while
> > creating executable and true while creating shared library (-shared
> option).
>
> That still requires the linker to at least do the full symbol search
> mandated by ELF, which lld still is missing. As such, the false positive
> rate for lld would be completely unacceptable.
>
> I'm not sure if the bfd or gold behavior is correct here, I can
> certainly think of situations where it is plainly wrong.
>
> Joerg
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150916/cc883e9f/attachment.html>