[all-commits] [llvm/llvm-project] da1b50: [libc++] Formalize what configurations are covered...

[Louis Dionne via All-commits]

  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: da1b50d7df213a3eaf583d576b8d7d2ec77bd97f
      https://github.com/llvm/llvm-project/commit/da1b50d7df213a3eaf583d576b8d7d2ec77bd97f
  Author: Louis Dionne <ldionne.2 at gmail.com>
  Date:   2020-11-27 (Fri, 27 Nov 2020)

  Changed paths:
    M libcxx/lib/abi/CMakeLists.txt
    A libcxx/lib/abi/x86_64-apple-darwin.libcxxabi.v1.stable.exceptions.no_new_in_libcxx.abilist
    R libcxx/lib/abi/x86_64-apple-darwin.v1.abilist
    A libcxx/lib/abi/x86_64-unknown-linux-gnu.libcxxabi.v1.stable.exceptions.no_new_in_libcxx.abilist
    R libcxx/lib/abi/x86_64-unknown-linux-gnu.v1.abilist
    M libcxx/utils/ci/run-buildbot

  Log Message:
  -----------
  [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