aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Object/XCOFFObjectFile.cpp
diff options
context:
space:
mode:
authorLouis Dionne <ldionne.2@gmail.com>2020-11-26 15:00:42 -0500
committerLouis Dionne <ldionne.2@gmail.com>2020-11-27 10:01:07 -0500
commitda1b50d7df213a3eaf583d576b8d7d2ec77bd97f (patch)
treefc5d0e89f37d715375bdd3b50a24f9eb3b5eade1 /llvm/lib/Object/XCOFFObjectFile.cpp
parent527a7fdfbd7461e2aaa9eb279543c5d9dc8efa5a (diff)
downloadllvm-da1b50d7df213a3eaf583d576b8d7d2ec77bd97f.zip
llvm-da1b50d7df213a3eaf583d576b8d7d2ec77bd97f.tar.gz
llvm-da1b50d7df213a3eaf583d576b8d7d2ec77bd97f.tar.bz2
[libc++] Formalize what configurations are covered by the ABI lists
By encoding ABI-affecting properties in the name of the ABI list, it makes it clear when an ABI list test should or should not be available, and what results we should expect. Note that we clearly don't encode all ABI-affecting parameters in the name right now -- I just ported over what we supported in the code that was there previously. As we encounter configurations that we wish to support but produce different ABI lists, we can add those to the ABI identifier and start supporting them. This commit also starts checking the ABI list in the CI jobs that run a supported configuration. Eventually, all configurations should have a generated ABI list and the test should even run implicitly as part of the Lit test suite. Differential Revision: https://reviews.llvm.org/D92194
Diffstat (limited to 'llvm/lib/Object/XCOFFObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions