maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/FileCheck/check-not-diaginfo.txt

11 lines
310 B
Plaintext
Raw Normal View History

Prefix failing commands with not to make clear they are expected to fail. llvm-svn: 185554
2013-07-04 00:41:29 +08:00
; RUN: not FileCheck -input-file %s %s 2>&1 | FileCheck -check-prefix DIAG %s
Remove SMLoc paired with CHECK-NOT patterns. Not functionality change. Pattern has source location by itself. After adding a trivial method to retrieve it, it's unnecessary to pair a source location for CHECK-NOT patterns. One thing revised after this is the diagnostic info is more accurate by pointing to the start of the CHECK-NOT pattern instead of the end of the CHECK-NOT pattern. E.g. diagnostic message previously looks like <stdin>:1:1: error: CHECK-NOT: string occurred! test ^ test.txt:1:16: note: CHECK-NOT: pattern specified here CHECK-NOT: test ^ is changed to <stdin>:1:1: error: CHECK-NOT: string occurred! test ^ test.txt:1:12: note: CHECK-NOT: pattern specified here CHECK-NOT: test ^ llvm-svn: 180578
2013-04-26 05:31:34 +08:00
CHECK-NOT: test
[FileCheck] Implement -v and -vv for tracing matches -v prints all directive pattern matches. -vv additionally prints info that might be noise to users but that can be helpful to FileCheck developers. To maximize code reuse and to make diagnostics more consistent, this patch also adjusts and extends some of the existing diagnostics. CHECK-NOT failures now report variables uses. Many more diagnostics now report the check prefix and kind of directive. Reviewed By: probinson Differential Revision: https://reviews.llvm.org/D47114 llvm-svn: 336967
2018-07-13 11:08:23 +08:00
DIAG: error: CHECK-NOT: excluded string found in input
DIAG-NEXT: CHECK-NOT: test
DIAG-NEXT: {{^ \^}}
DIAG-NEXT: note: found here
Remove SMLoc paired with CHECK-NOT patterns. Not functionality change. Pattern has source location by itself. After adding a trivial method to retrieve it, it's unnecessary to pair a source location for CHECK-NOT patterns. One thing revised after this is the diagnostic info is more accurate by pointing to the start of the CHECK-NOT pattern instead of the end of the CHECK-NOT pattern. E.g. diagnostic message previously looks like <stdin>:1:1: error: CHECK-NOT: string occurred! test ^ test.txt:1:16: note: CHECK-NOT: pattern specified here CHECK-NOT: test ^ is changed to <stdin>:1:1: error: CHECK-NOT: string occurred! test ^ test.txt:1:12: note: CHECK-NOT: pattern specified here CHECK-NOT: test ^ llvm-svn: 180578
2013-04-26 05:31:34 +08:00
DIAG-NEXT: CHECK-NOT: test
DIAG-NEXT: {{^ \^}}