aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Reader/BitcodeReader.cpp
diff options
context:
space:
mode:
authorDavid Spickett <david.spickett@linaro.org>2024-05-01 15:10:01 +0100
committerGitHub <noreply@github.com>2024-05-01 15:10:01 +0100
commit167b50669c03ad888bf2f00c61424bedac43a050 (patch)
treeb917d8826455447037240fd1c4285c8503494cd9 /llvm/lib/Bitcode/Reader/BitcodeReader.cpp
parente312f0723cebcfbc899b7b69538dfe86f426d0b4 (diff)
downloadllvm-167b50669c03ad888bf2f00c61424bedac43a050.zip
llvm-167b50669c03ad888bf2f00c61424bedac43a050.tar.gz
llvm-167b50669c03ad888bf2f00c61424bedac43a050.tar.bz2
[libcxx][ci] In picolib build, ask clang for the normalised triple (#90722)
This is needed for a workaround to make sure the link later succeeds. I don't know the reason for that but it is definitely needed. https://github.com/llvm/llvm-project/pull/89234 will/wants to correct the triple normalisation for -none- and this means that clang prior to 19, and clang 19 and above will have different answers and therefore different library paths. I don't want to bootstrap a clang just for libcxx CI, or require that anyone building for Arm do the same, so ask the compiler what the triple should be. This will be compatible with 17 and 19 when we do update to that version. I'm assuming $CC is what anyone locally would set to override the compiler, and `cc` is the binary name in our CI containers. It's not perfect but it should cover most use cases.
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions