[lit] Stop supporting triple substrings in UNSUPPORTED and XFAIL
authorPaul Robinson <paul.robinson@sony.com>
Wed, 4 Jan 2023 19:35:59 +0000 (11:35 -0800)
committerPaul Robinson <paul.robinson@sony.com>
Thu, 19 Jan 2023 16:35:02 +0000 (08:35 -0800)
commita0f8bdbb18a82ec150515d24f6eefb3519d4459a
treed7ae1c8b247603fdc5187363f5486c453f296a19
parentfd26eee486ed81a2477e28d069fb68072fd7b2a2
[lit] Stop supporting triple substrings in UNSUPPORTED and XFAIL

AFAICT all in-tree lit tests have been converted to use `target=...`
and so there is no longer any need for triples being special.
Some project config files still define their own features based on
the triple, but those are normal feature words (although now are
redundant with target= checks).

Downstream tests that use triple substrings will need to convert.
For example:
    UNSUPPORTED: -aix
    XFAIL: arm
becomes
    UNSUPPORTED: target={{.*}}-aix{{.*}}
    XFAIL: target=arm{{.*}}

You can do
    git log --grep "special handling for triples"
to find many examples of updates to the upstream tests.

https://discourse.llvm.org/t/rfc-lits-requires-and-triples/66041

Differential Revision: https://reviews.llvm.org/D141007
llvm/docs/ReleaseNotes.rst
llvm/utils/lit/lit/BooleanExpression.py
llvm/utils/lit/lit/Test.py