aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
diff options
context:
space:
mode:
authorLouis Dionne <ldionne@apple.com>2020-09-09 16:14:56 -0400
committerLouis Dionne <ldionne@apple.com>2020-09-10 08:17:26 -0400
commitec46cfefe80d58cdc7068ad4e4f8efde6d94d835 (patch)
treefe6d028991467d816671c79d632752b533792b46 /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
parent8c0bbbade169d9fda6cac8f181660009599a7656 (diff)
downloadllvm-ec46cfefe80d58cdc7068ad4e4f8efde6d94d835.zip
llvm-ec46cfefe80d58cdc7068ad4e4f8efde6d94d835.tar.gz
llvm-ec46cfefe80d58cdc7068ad4e4f8efde6d94d835.tar.bz2
[libcxx] Simplify back-deployment testing
The needs of back-deployment testing currently require two different ways of running the test suite: one based on the deployment target, and one based on the target triple. Since the triple includes all the information we need, it's better to have just one way of doing things. Furthermore, `--param platform=XXX` is also supersedded by using the target triple. Previously, this parameter would serve the purpose of controling XFAILs for availability markup errors, however it is possible to achieve the same thing by using with_system_cxx_lib only and using .verify.cpp tests instead, as explained in the documentation changes. The motivation for this change is twofold: 1. This part of the Lit config has always been really confusing and complicated, and it has been a source of bugs in the past. I have simplified it iteratively in the past, but the complexity is still there. 2. The deployment-target detection started failing in weird ways in recent Clangs, breaking our CI. Instead of band-aid patching the issue, I decided to remove the complexity altogether by using target triples even on Apple platforms. A follow-up to this commit will bring the test suite in line with the recommended way of handling availability markup tests.
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions