Displaying 2 results from an estimated 2 matches for "defpat".
Did you mean:
defeat
2020 Feb 03
2
[RFC][FileCheck] New option to negate check patterns
...ble. But adding a way to define a pattern that is independent of
> the input text seems like it could be useful.
>
>
>
> I’d suggest that initially at least, the define-a-pattern directive would
> take only “immediate” text, no embedded regexes. That is, you could do
>
> DEFPAT[MYPATTERN]: Define a pattern here
>
> but you couldn’t do
>
> DEFPAT[MYPATTERN]: Define {{some|any}} pattern here
>
> although it might be reasonable to allow
>
> DEFPAT[PATTERN1]: some
>
> DEFPAT[PATTERN2]: Define [[PATTERN1]] pattern here
>
> as the...
2020 Jan 31
2
[RFC][FileCheck] New option to negate check patterns
Hi all,
> I feel it might be confusing to have a CHECK becomes effectively a CHECK-NOT,
> especially if the RUN line is far from the CHECK line (which is often the case when
> a single RUN line drives several groups of CHECK directives (e.g. code generation
> tested for several functions for a specific feature, like PIC). You also loose control
> on where the NOT should be: