diff options
author | Hans Wennborg <hans@chromium.org> | 2020-07-28 12:26:37 +0200 |
---|---|---|
committer | Hans Wennborg <hans@chromium.org> | 2020-07-28 12:33:51 +0200 |
commit | 7e8d5a90f2c101388d3b0bbce8555e871c670232 (patch) | |
tree | 102d4a732115e7db7b43f22db33e7f731f411677 /llvm/lib/Target/PowerPC/Disassembler/PPCDisassembler.cpp | |
parent | 93b7915504b708f39a75d72e08448443a899345e (diff) | |
download | llvm-7e8d5a90f2c101388d3b0bbce8555e871c670232.zip llvm-7e8d5a90f2c101388d3b0bbce8555e871c670232.tar.gz llvm-7e8d5a90f2c101388d3b0bbce8555e871c670232.tar.bz2 |
Avoid use of std::make_unique in compiler-rt/lib/scudo/standalone/tests/combined_test.cpp
make_unique is a C++14 feature, and this prevents us from building on
Ubuntu Trusty. While we do use a C++14 compatible toolchain for building
in general, we fall back to the system toolchain for building the
compiler-rt tests.
The reason is that those tests get cross-compiled for e.g. 32-bit and
64-bit x86, and while the toolchain provides libstdc++ in those
flavours, the resulting compiler-rt test binaries don't get RPATH set
and so won't start if they're linked with that toolchain.
We've tried linking the test binaries against libstdc++ statically, by
passing COMPILER_RT_TEST_COMPILER_CFLAGS=-static-libstdc++. That mostly
works, but some test targets append -lstdc++ to the compiler invocation.
So, after spending way too much time on this, let's just avoid C++14
here for now.
Diffstat (limited to 'llvm/lib/Target/PowerPC/Disassembler/PPCDisassembler.cpp')
0 files changed, 0 insertions, 0 deletions