diff options
| author | Chandler Carruth <chandlerc@gmail.com> | 2013-06-23 11:28:48 +0000 |
|---|---|---|
| committer | Chandler Carruth <chandlerc@gmail.com> | 2013-06-23 11:28:48 +0000 |
| commit | 363817092e1d41a8370a2177e9355540d1a8e8f8 (patch) | |
| tree | 74771fd8011ea1eda9a10b7ee4b6bc76f8b192d1 /clang/lib/Frontend/CompilerInvocation.cpp | |
| parent | 8907811e4bbd6b67aa5e33a75156846df1e9a879 (diff) | |
| download | llvm-363817092e1d41a8370a2177e9355540d1a8e8f8.zip llvm-363817092e1d41a8370a2177e9355540d1a8e8f8.tar.gz llvm-363817092e1d41a8370a2177e9355540d1a8e8f8.tar.bz2 | |
Fix the addition of Clang's profile runtime library to the link step
when specifying --coverage (or related) flags.
The system for doing this was based on the old LLVM-hosted profile_rt
library, and hadn't been updated for Linux to use the new compiler-rt
library. Also, it couldn't possibly work on multiarch or biarch systems
in many cases. The whole thing now works much the same as the sanitizer
libraries that are built and used out of the compiler-rt repo.
Note that other target OSes haven't been updated because I don't know if
they're doing anything special with the installation path of profile_rt.
I suspect however that *all* of these are wrong and would encourage
maintainers of each target to take a hard look at how compiler-rt
runtime libraries are linked on their platforms.
llvm-svn: 184666
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions