Debian Codegraph @

gcc/testsuite/c-c++-common/diagnostic-format-sarif-file-timevars-2.c

raw
1 /* As per diagnostic-format-sarif-file-timevars-1.c, but
2 adding -ftime-report-details. */
3
4 /* { dg-do compile } */
5 /* { dg-options "-fdiagnostics-format=sarif-file -ftime-report -ftime-report-details" } */
6
7 #warning message
8
9 /* Verify that some JSON was written to a file with the expected name. */
10 /* { dg-final { verify-sarif-file } } */
11
12 /* We expect various properties.
13 The indentation here reflects the expected hierarchy, though these tests
14 don't check for that, merely the string fragments we expect.
15
16 { dg-final { scan-sarif-file {"invocations": } } }
17 { dg-final { scan-sarif-file {"properties": } } }
18 { dg-final { scan-sarif-file {"gcc/timeReport": } } }
19 { dg-final { scan-sarif-file {"timevars": } } }
20 { dg-final { scan-sarif-file {"name": "TOTAL",} } }
21 */