[llvm-dev] FileCheck DAG match N lines

[Joel E. Denny via llvm-dev]

Hi David,

This use case has come up several times.  I've not heard of any existing
solution.

I've been thinking we should have CHECK-DAG-NEXT blocks.  Likewise, for
unordered text on a single line, we'd have CHECK-DAG-SAME blocks.  In both
these cases, we'd have the question of how to handle the first match.
Would it be bound by the NEXT or SAME rule relative to the match preceding
the block?

If anyone wants to implement something like this, please cc me on the
discussion/review.  I'd like to make use of such a feature, and I have
ideas on how to address some of the subtleties, such as the question above.

Thanks.

Joel

On Wed, Nov 27, 2019 at 5:21 AM David Stenberg via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> Hi!
>
> If a test has output of the following form:
>
>   START
>   VALUE X1
>   VALUE X2
>   [...]
>   VALUE X_N
>   END
>
> where the order of X_1..X_N is not deterministic, is it possible to
> write FileCheck checks that verify that the "VALUE" lines occur in any
> order, with only one occurrence per line, and no other "VALUE" lines in
> between?
>
> One idea that was suggested to me was to write checks of the following
> form:
>
>   CHECK: START
>   CHECK-NOT: VALUE
>   CHECK-DAG: VALUE X1
>   CHECK-DAG: VALUE X2
>   [...]
>   CHECK-DAG: VALUE X_N
>   CHECK-NOT: VALUE
>   CHECK: END
>
> However, that for example matches on:
>
>   START
>   VALUE X1
>   VALUE X1
>   VALUE Foo
>   VALUE X3
>   VALUE X1
>   VALUE X2
>   END
>
> I have looked through the FileCheck documentation, but haven't found
> anything that describes a similar case.
>
> Are these sorts of checks achievable with FileCheck?
>
> Best regards,
> David
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191127/9cc5a378/attachment.html>