summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Support/LockFileManager.cpp
diff options
context:
space:
mode:
authorHans Wennborg <hans@hanshq.net>2018-08-16 14:54:37 +0000
committerHans Wennborg <hans@hanshq.net>2018-08-16 14:54:37 +0000
commit099600fc8bbaa6119792ab9a5b8217198b65f5f0 (patch)
treee11e369a694575760877433d483d83aba1df40d5 /llvm/lib/Support/LockFileManager.cpp
parentada3e3cdb3470886e2e683d5f35305a049ec6e2e (diff)
downloadbcm5719-llvm-099600fc8bbaa6119792ab9a5b8217198b65f5f0.tar.gz
bcm5719-llvm-099600fc8bbaa6119792ab9a5b8217198b65f5f0.zip
Merging r339874:
------------------------------------------------------------------------ r339874 | ldionne | 2018-08-16 14:44:28 +0200 (Thu, 16 Aug 2018) | 25 lines [libcxx] By default, do not use internal_linkage to hide symbols from the ABI Summary: https://reviews.llvm.org/D49240 led to symbol size problems in Chromium, and we expect this may be the case in other projects built in debug mode too. Instead, unless users explicitly ask for internal_linkage, we use always_inline like we used to. In the future, when we have a solution that allows us to drop always_inline without falling back on internal_linkage, we can replace always_inline by that. Note that this commit introduces a change in contract for existing libc++ users: by default, libc++ used to guarantee that TUs built with different versions of libc++ could be linked together. With the introduction of the _LIBCPP_HIDE_FROM_ABI_PER_TU macro, the default behavior is that TUs built with different libc++ versions are not guaranteed to link. This is a change in contract but not a change in behavior, since the current implementation still allows linking TUs built with different libc++ versions together. Reviewers: EricWF, mclow.lists, dexonsmith, hans, rnk Subscribers: christof, cfe-commits Differential Revision: https://reviews.llvm.org/D50652 ------------------------------------------------------------------------ llvm-svn: 339882
Diffstat (limited to 'llvm/lib/Support/LockFileManager.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud