[llvm-branch-commits] ELF: Add a -z glibc-228-compat flag for working around an old glibc bug. (PR #133532)

[Fangrui Song via llvm-branch-commits]

https://github.com/MaskRay requested changes to this pull request.

While at Google, I encountered this issue co-authored the glibc commit b5c45e83753b27dc538dff2d55d4410c385cf3a4.
I don’t believe this is relevant for upstream LLD, so I haven’t pursued submitting a linker patch.
The piece of LLD code is highly stable, so maintaining this as a Google-specific downstream patch should not pose challenges.

I understand that Google’s production environment is pinned to glibc 2.27, and updating glibc is complex and may not be an internal product priority,
However, I don’t believe this patch is suitable for upstream LLD. I hope this rejection highlights the importance of maintaining a more current glibc version, to any lead that might see this message.
https://sourceware.org/git/?p=glibc.git;a=log;h=refs/heads/google/grte/v5-2.27/master


https://github.com/llvm/llvm-project/pull/133532