message-length.c revision 4fcfde4d5c8f25e40720972a5543d538a0dcb220 
1// RUN: clang -fsyntax-only -fmessage-length=72 %s 2>&1 | FileCheck -strict-whitespace %s
2// RUN: clang -fsyntax-only -fmessage-length=1 %s
3
4// Hack so we can check things better, force the file name and line.
5# 1 "FILE" 1
6
7/* It's tough to verify the results of this test mechanically, since
8   the length of the filename (and, therefore, how the word-wrapping
9   behaves) changes depending on where the test-suite resides in the
10   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
31// CHECK: FILE:23:78
32// CHECK: {{^  ...// some long comment text and a brace, eh {} }}
33