Displaying 3 results from an estimated 3 matches for "1683e704".
Did you mean:
168304
2016 May 26
0
RFC: FileCheck Enhancements
7. Wildcard for prefixes - If some statements should be checked
regardless prefix, it should be used //{{*}}, //{{*}}-NEXT, //{{*}}-SAME
and etc.
> 8. Prefix with regular expressions - If statement should be checked
> if prefix matches some regular expression, it should be used {{regex}}:,
> {{regex}}-NEXT and etc.
>
>
>
>
I, too, think wildcard and regular
2016 May 26
3
RFC: FileCheck Enhancements
...run to accomplish the same thing, and
many tests do that today. (e.g. "FileCheck --check-prefix=CHECK
--check-prefix=SSE --check-prefix=SSE3").
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160526/1683e704/attachment.html>
2016 May 24
12
RFC: FileCheck Enhancements
Hi everyone,
There was idea to add new directives to FileCheck:
1. Directive to use some patterns as named template with or without parameters.
2. CHECK-INCLUDE - Directive to include other file with checks to another.
3. Expressions repeat for CHECK - If statement should be checked several times repeat modifiers {n}, {n,m} , {,n}, {n,}, *, + can be used.
4. Repeat in