diff options
| author | Fangrui Song <i@maskray.me> | 2021-08-27 08:53:55 -0700 |
|---|---|---|
| committer | Fangrui Song <i@maskray.me> | 2021-08-27 08:53:55 -0700 |
| commit | 83dfa0d098f3176607aecea815eb87979953cdb5 (patch) | |
| tree | 1a129e82581f2e4bc591db273a8edde1d7f2ff7c /lldb/source/Commands/CommandObjectProcess.cpp | |
| parent | 77b6a4bde4de37bd77f4846b3c31c1d0633a8f13 (diff) | |
| download | llvm-83dfa0d098f3176607aecea815eb87979953cdb5.zip llvm-83dfa0d098f3176607aecea815eb87979953cdb5.tar.gz llvm-83dfa0d098f3176607aecea815eb87979953cdb5.tar.bz2 | |
[MC] Change ELFOSABI_NONE to ELFOSABI_GNU for STB_GNU_UNIQUE
Similar to D97976.
On Linux, most GCC installations are configured with
`--enable-gnu-unique-object` and such GCC emits `@gnu_unique_object` assembly.
The feature is highly controversial and disliked by many folks.
(On glibc DF_1_NODELETE is implicitly enabled and makes dlclose a no-op).
In llvm-project STB_GNU_UNIQUE is assembly only. Clang does not use STB_GNU_UNIQUE.
Use ELFOSABI_GNU to match GNU as behavior and avoid collision with other
OSABI binding values.
Reviewed By: jrtc27
Differential Revision: https://reviews.llvm.org/D107861
Diffstat (limited to 'lldb/source/Commands/CommandObjectProcess.cpp')
0 files changed, 0 insertions, 0 deletions