aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ObjectFile/ELF/ObjectFileELF.cpp
diff options
context:
space:
mode:
authorChuanqi Xu <yedeng.yd@linux.alibaba.com>2023-03-13 15:43:08 +0800
committerChuanqi Xu <yedeng.yd@linux.alibaba.com>2023-03-13 15:54:40 +0800
commit2e9977c2815653c141c6c060c4e0ab6c0db27911 (patch)
tree389b35dbf6dbfa3fe1bd8a1293b0f0611637682a /lldb/source/Plugins/ObjectFile/ELF/ObjectFileELF.cpp
parent2869d31a7ac1e4748d171711614e9a89dfc0f75a (diff)
downloadllvm-2e9977c2815653c141c6c060c4e0ab6c0db27911.zip
llvm-2e9977c2815653c141c6c060c4e0ab6c0db27911.tar.gz
llvm-2e9977c2815653c141c6c060c4e0ab6c0db27911.tar.bz2
[C++20] [Modules] Treat module linkage as formal linkage only
Close https://github.com/llvm/llvm-project/issues/61321 There are two linkage modes in clang now: one for internal linkage and one for formal linkage. The internal linkage is for the implementation details and the formal linkage is for the consistency with the C++ standard. Since we previously implemented the strong ownership for modules, the module linkage is not meaningful for linkers any more. So the module linkage should only be used for formal linkage.
Diffstat (limited to 'lldb/source/Plugins/ObjectFile/ELF/ObjectFileELF.cpp')
0 files changed, 0 insertions, 0 deletions