42 lines · c
1// RUN: not %clang_cc1 -fmessage-length=72 %s 2>&1 | FileCheck -strict-whitespace %s2// RUN: not %clang_cc1 -fmessage-length=1 %s3// RUN: not %clang_cc1 -fmessage-length=8 %s 2>&1 | FileCheck -check-prefix=CHECK-DOT %s4// Hack so we can check things better, force the file name and line.5# 1 "FILE" 16 7/* It's tough to verify the results of this test mechanically, since8 the length of the filename (and, therefore, how the word-wrapping9 behaves) changes depending on where the test-suite resides in the10 file system. */11void f(int, float, char, float);12 13void g() {14 int (*fp1)(int, float, short, float) = f;15 16 int (*fp2)(int, float, short, float) = f;17}18 19void a_func_to_call(int, int, int);20 21void a_very_long_line(int *ip, float *FloatPointer) {22 for (int ALongIndexName = 0; ALongIndexName < 100; ALongIndexName++) if (ip[ALongIndexName] == 17) a_func_to_call(ip == FloatPointer, ip[ALongIndexName], FloatPointer[ALongIndexName]);23 24 25 int array0[] = { [3] 3, 5, 7, 4, 2, 7, 6, 3, 4, 5, 6, 7, 8, 9, 12, 345, 14, 345, 789, 234, 678, 345, 123, 765, 234 };26}27 28#pragma STDC CX_LIMITED_RANGE // some long comment text and a brace, eh {}29 30// CHECK: FILE:23:7831// CHECK: {{^ 23 | ...// some long comment text and a brace, eh {}}}32 33struct A { int x; };34void h(struct A *a) {35 // CHECK-DOT: member36 // CHECK-DOT: reference37 // CHECK-DOT: type38 (void)a39 .40 x;41}42