This is an archive of the discontinued LLVM Phabricator instance.

[ELF] Avoid wrapping unreferenced lazy symbols
ClosedPublic

Authored by smeenai on Feb 2 2022, 12:10 AM.

Details

Summary

There's a couple of motivations here:

  • LLD 12 (which I was originally testing with) was adding an undefined symbol to the symbol table if you attempted to wrap an unreferenced lazy symbol, which would later break --no-allow-shlib-undefined. LLD on main actually produces a weak undefined symbol, so this doesn't break anyway, but it's cleaner to not have the weak undefined symbol as well. The new behavior also matches bfd and gold.
  • PROVIDE in a linker script referencing a wrapped symbol would think that an otherwise-unreferenced lazy symbol which was wrapped was actually referenced, and therefore proceed with the definition, which goes against expectations. The new behavior also matches bfd and gold.

Diff Detail

Event Timeline

smeenai created this revision.Feb 2 2022, 12:10 AM
smeenai requested review of this revision.Feb 2 2022, 12:10 AM
Herald added a project: Restricted Project. · View Herald TranscriptFeb 2 2022, 12:10 AM
smeenai edited the summary of this revision. (Show Details)Feb 2 2022, 12:14 AM

Implementation looks good to me. It may be worth writing a test involving LTO, for example a definition of lazy in a bitcode archive. As I understand the implementation this should work, but it may be worth having a regression test to catch it if it breaks.

smeenai updated this revision to Diff 405361.Feb 2 2022, 10:42 AM

Add bitcode test

Implementation looks good to me. It may be worth writing a test involving LTO, for example a definition of lazy in a bitcode archive. As I understand the implementation this should work, but it may be worth having a regression test to catch it if it breaks.

Thanks for the suggestion. I added a test involving bitcode as well. (I didn't duplicate every single test scenario, because that felt like overkill, but the basic archive and --start-lib cases are covered.)

MaskRay added inline comments.Feb 2 2022, 7:57 PM
lld/ELF/Driver.cpp
2053

A lazy weak symbol indicates there is an undefined weak reference from a .o or .so file.

If referenced by a .o, we should wrap the lazy symbol (which will be converted to an Undefined in demoteSharedSymbols (the function is a bit misnamed after my recent changes. I plan to rename it to demoteSymbols (LG? @peter.smith))

If referenced by a .so but not by a .o, isUsedInRegularObj is false. We should not wrap it. The behavior matches GNU ld.

lld/test/ELF/wrap-lazy.test
8

Thanks for adding bitcode tests.

I think having both archive and --start-lib tests are redundant. You may remove archive tests.

llvm-ar crs x.a needs to remove the archive first, otherwise there is a risk that a dangling archive with more symbols can cause different symbol resolution results.

11

Prefer llvm-readelf -s:

  • .symtab is a superset of .dynsym . We usually want to know information about all symbols, including the part not in .dynsym. The full information is sufficient to infer .dynsym
  • We want to know whether a symbol is defined or undefined, STB_GLOBAL or STB_WEAK. nm output is distorted by the BFD library a bit, so there is some information loss.
44

Calling it lib.s may be slightly confusing since I'd imagine lib.s is used with the archive semantics while the tests don't use its archive semantics.

50

Add

#--- weakref.s
.weak lazy
  jmp lazy

Add two RUN lines like %tlib.o %tweakref.o %tliblazy.a --wrap lazy and %tlib.o %tweakref.so %tliblazy.a --wrap lazy

MaskRay added inline comments.Feb 2 2022, 8:00 PM
lld/ELF/Driver.cpp
2051

This is now called "extracted" :)

Consider deleting wrap-with-archive.s (D56110) since the new wrap-lazy.test is more comprehensive.

smeenai added inline comments.Feb 3 2022, 10:36 AM
lld/test/ELF/wrap-lazy.test
8

Do you mean archive tests for the bitcode specifically, or all the other archive tests as well?

MaskRay added inline comments.Feb 3 2022, 11:00 AM
lld/test/ELF/wrap-lazy.test
8

Either only keep --start-lib tests, or only keep archive tests.

smeenai updated this revision to Diff 405835.Feb 3 2022, 5:10 PM

Address review comments

smeenai marked 7 inline comments as done.Feb 3 2022, 5:10 PM

Consider deleting wrap-with-archive.s (D56110) since the new wrap-lazy.test is more comprehensive.

That test seems to be covering the interaction between linker-defined symbols and wrapping specifically (see D56110). I undid the code change from D56110, and wrap-with-archive.s failed but wrap-lazy.test still passed. I could theoretically extend wrap-lazy.test to cover that case as well, but it'd be mixing multiple concerns into one test.

MaskRay accepted this revision.Feb 3 2022, 7:05 PM
MaskRay added inline comments.
lld/test/ELF/wrap-lazy.test
6

Drop linux-gnu to make it clear this is a generic ELF behavior.

22

Create ld.lld -shared ... -o %tweakref.so and additionally test %tweakref.so --start-lib %tlazy.o --wrap lazy

28
This revision is now accepted and ready to land.Feb 3 2022, 7:05 PM
smeenai added inline comments.Feb 3 2022, 7:08 PM
lld/test/ELF/wrap-lazy.test
6

Does just -triple=x86_64 imply ELF by default, or is there some way to make it explicit?

MaskRay added inline comments.Feb 3 2022, 7:14 PM
lld/test/ELF/wrap-lazy.test
6

-triple=x86_64 implies ELF like -triple=x86_64-elf

smeenai updated this revision to Diff 405861.Feb 3 2022, 8:00 PM

Address comments

smeenai marked 3 inline comments as done.Feb 3 2022, 8:00 PM
smeenai added inline comments.
lld/test/ELF/wrap-lazy.test
22

I added this, but I'm not 100% sure it's what you meant. Could you double check?

MaskRay accepted this revision.Feb 3 2022, 10:36 PM
MaskRay added inline comments.
lld/test/ELF/wrap-lazy.test
24

If a produced shared object is used as input to another link, set soname to a fixed value so that the subsequent link will not get DT_NEEDED of varying lengths.

smeenai updated this revision to Diff 406139.Feb 4 2022, 6:09 PM

Add soname

smeenai marked 2 inline comments as done.Feb 4 2022, 6:10 PM

Thanks for the quick review and all the suggestions!

This revision was landed with ongoing or failed builds.Feb 4 2022, 6:14 PM
This revision was automatically updated to reflect the committed changes.