File: opt-color.txt

package info (click to toggle)
llvm-toolchain-18 1%3A18.1.8-20
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,909,296 kB
  • sloc: cpp: 6,667,975; ansic: 1,440,452; asm: 883,619; python: 230,549; objc: 76,880; f90: 74,238; lisp: 35,989; pascal: 16,571; sh: 10,229; perl: 7,459; ml: 5,047; awk: 3,523; makefile: 2,992; javascript: 2,149; xml: 892; fortran: 649; cs: 573
file content (22 lines) | stat: -rw-r--r-- 998 bytes parent folder | download | duplicates (27) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
 
; Create a case that produces a simple diagnostic.
; RUN: echo foo > %t.in
; CHECK: bar

; Run without and with -color.  In the former case, FileCheck should suppress
; color in its diagnostics because stderr is a file.
; RUN: %ProtectFileCheckOutput not FileCheck %s < %t.in 2> %t.no-color
; RUN: %ProtectFileCheckOutput not FileCheck -color %s < %t.in 2> %t.color

; Check whether color was produced.
; RUN: FileCheck -check-prefix NO-COLOR %s < %t.no-color
; RUN: FileCheck -check-prefix COLOR %s < %t.color

; Make sure our NO-COLOR and COLOR patterns are sane: they don't match the
; opposite cases.
; RUN: not FileCheck -check-prefix COLOR %s < %t.no-color
; RUN: not FileCheck -check-prefix NO-COLOR %s < %t.color

; I don't know of a good way to check for ANSI color codes, so just make sure
; some new characters show up where those codes should appear.
; NO-COLOR: : error: CHECK: expected string not found in input
; COLOR: : {{.+}}error: {{.+}}CHECK: expected string not found in input