Displaying 3 results from an estimated 3 matches for "implicit_task_id".
2018 May 07
0
RFC: [FileCheck] CHECK-DAG for multiple occurrences of string
> 1. In a CHECK-DAG group, don't let the matches for patterns overlap.
> 2. Add a new CHECK-DAG-N directive, where N is some integer, to express
> that a pattern must have N non-overlapping matches.
I think #1 is much more intuitive and easy to describe/document than #2.
Changing the meaning of DAG in that way is highly unlikely to affect any
existing test, IMO. And if it does, my
2018 May 04
5
RFC: [FileCheck] CHECK-DAG for multiple occurrences of string
Hi,
Using FileCheck, I have not found a way to make a group of CHECK-DAG
directives match multiple occurrences of a string. For example, I naively
thought the following would match successfully:
```
$ cat checks.txt
// CHECK: start
// CHECK-DAG: foo
// CHECK-DAG: foo
// CHECK-DAG: bar
// CHECK-NEXT: end
$ cat input.txt
start
foo
bar
foo
end
$ FileCheck --input-file=input.txt checks.txt
2018 May 11
3
RFC: [FileCheck] CHECK-DAG for multiple occurrences of string
...st an incorrect attempt at the original use case I
wanted to address.
For example,
projects/openmp/runtime/test/ompt/parallel/not_enough_threads.c repeats the
following three times:
```
// CHECK-DAG: {{^}}[[THREAD_ID:[0-9]+]]: ompt_event_implicit_task_begin:
parallel_id=[[PARALLEL_ID]], task_id=[[IMPLICIT_TASK_ID:[0-9]+]]
// CHECK-DAG: {{^}}[[THREAD_ID]]: ompt_event_barrier_begin:
parallel_id=[[PARALLEL_ID]], task_id=[[IMPLICIT_TASK_ID]]
```
The author was obviously expecting CHECK-DAG not to permit overlapping
matches and wanted to check that the above lines appeared three times.
Specifically, he's ex...