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

[Shridhar Joshi via llvm-commits]

joshishr added a comment.

In http://reviews.llvm.org/D12226#238177, @joerg wrote:

> The undefined-shlib case makes no sense. That's exactly the case I am talking about.


--[no]-allow-shlib-undefined option is shared library specific. --unresolved-symbols=ignore-in-object-files option may look equivalent to --allow-shlib-undefined but it is not exactly equivalent since it will report undefined symbols in object files while allowing undefined symbols from dependent shared libraries linked against. So --[no]-allow-shlib-undefined and --unresolved-symbols options serves different unique purpose. Comparatively later option has lot more use case as it allows unresolved symbols in executable as well. This adds use case to defer symbol resolution till run time by pre-loading shared libraries or through dlopen().

Some of the use cases in my test case using --[no]-allow-shlib-undefined may look making no sense but I have added them just for completeness of testing all combinations.


http://reviews.llvm.org/D12226