diff options
| author | Chuanqi Xu <yedeng.yd@linux.alibaba.com> | 2022-07-26 18:26:35 +0800 |
|---|---|---|
| committer | Chuanqi Xu <yedeng.yd@linux.alibaba.com> | 2022-07-26 18:30:48 +0800 |
| commit | 15ddc09ef9b05ffd5398165049b5202264fa203a (patch) | |
| tree | dac487e024cd94c98381cdc33db9b70dd59e3765 /llvm/lib/Bitcode/Reader/BitcodeReader.cpp | |
| parent | 93f8657c743ba9ce9696e5f0c9487207cf8ccb6b (diff) | |
| download | llvm-15ddc09ef9b05ffd5398165049b5202264fa203a.zip llvm-15ddc09ef9b05ffd5398165049b5202264fa203a.tar.gz llvm-15ddc09ef9b05ffd5398165049b5202264fa203a.tar.bz2 | |
[C++20] [Modules] Handle linkage properly for specializations when overloading
Currently, the semantics of linkage in clang is slightly
different from the semantics in C++ spec. In C++ spec, only names
have linkage. So that all entities of the same should share
one linkage. But in clang, different entities of the same could
have different linkage.
It would break a use case where the template have external linkage and
its specialization have internal linkage due to its type argument is
internal linkage. The root cause is that the semantics of internal
linkage in clang is a mixed form of internal linkage and TU-local in
C++ spec. It is hard to solve the root problem and I tried to add a
workaround inplace.
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions