diff options
| author | Vedant Kumar <vsk@apple.com> | 2017-09-12 19:15:31 +0000 |
|---|---|---|
| committer | Vedant Kumar <vsk@apple.com> | 2017-09-12 19:15:31 +0000 |
| commit | 796a13fcde6b4ebd8d6fc1b9f00899f2a6d573c0 (patch) | |
| tree | 6ab61e7cb877c717d99f353e3b196fe94caceea6 /clang-tools-extra/clang-tidy/cppcoreguidelines/OwningMemoryCheck.cpp | |
| parent | c589f5f87559c5e32a5dbc3fadcb9257140ce72f (diff) | |
| download | bcm5719-llvm-796a13fcde6b4ebd8d6fc1b9f00899f2a6d573c0.tar.gz bcm5719-llvm-796a13fcde6b4ebd8d6fc1b9f00899f2a6d573c0.zip | |
[Driver] Darwin: Link in the profile runtime archive first
While building a project with code coverage enabled, we can link in
dependencies which export a weak definition of __llvm_profile_filename.
After r306710, linking in the profiling runtime could pull in a weak
definition of this symbol from a dependency, instead of from within the
runtime's archive.
This inconsistency causes issues during API verification, and is also a
practical problem (the symbol would go missing were the dependent dylib
to be switched out). Introduce a LinkFirst runtime link option to make
sure we always search the profiling runtime for this symbol first.
rdar://problem/33271080
Differential Revision: https://reviews.llvm.org/D35385
llvm-svn: 313065
Diffstat (limited to 'clang-tools-extra/clang-tidy/cppcoreguidelines/OwningMemoryCheck.cpp')
0 files changed, 0 insertions, 0 deletions
