maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/Misc/macro-backtrace.c

58 lines
2.9 KiB
C
Raw Normal View History

Fold two run lines into a single logical one, and move them down below the important code in this test to make the test more stable. Now adding further tests won't shift the line numbers occuring in the diagnostic output. llvm-svn: 142118
2011-10-16 15:20:21 +08:00
// Tests for macro expansion backtraces. The RUN and CHECK lines are grouped
// below the test code to reduce noise when updating them.
Introduce a limit on the depth of the macro instantiation backtrace printed in a diagnostic, similar to the limit we already have on the depth of the template instantiation backtrace. The macro instantiation backtrace is limited to 10 "instantiated from:" diagnostics; when it's longer than that, we'll show the first half, then say how many were suppressed, then show the second half. The limit can be changed with -fmacro-instantiation-limit=N, and turned off with N=0. This eliminates a lot of note spew with libraries making use of the Boost.Preprocess library. llvm-svn: 103014
2010-05-05 01:13:42 +08:00
#define M1(A, B) ((A) < (B))
#define M2(A, B) M1(A, B)
#define M3(A, B) M2(A, B)
#define M4(A, B) M3(A, B)
#define M5(A, B) M4(A, B)
#define M6(A, B) M5(A, B)
#define M7(A, B) M6(A, B)
#define M8(A, B) M7(A, B)
#define M9(A, B) M8(A, B)
#define M10(A, B) M9(A, B)
#define M11(A, B) M10(A, B)
#define M12(A, B) M11(A, B)
void f(int *ip, float *fp) {
Fold two run lines into a single logical one, and move them down below the important code in this test to make the test more stable. Now adding further tests won't shift the line numbers occuring in the diagnostic output. llvm-svn: 142118
2011-10-16 15:20:21 +08:00
if (M12(ip, fp)) { }
Add a prefix to the existing test to prepare for more tests of other backtrace behavior. llvm-svn: 142119
2011-10-16 15:20:23 +08:00
// RUN: %clang_cc1 -fsyntax-only -fmacro-backtrace-limit 5 %s 2>&1 \
// RUN: | FileCheck %s -check-prefix=CHECK-LIMIT
// CHECK-LIMIT: macro-backtrace.c:18:7: warning: comparison of distinct pointer types ('int *' and 'float *')
// CHECK-LIMIT: if (M12(ip, fp)) { }
Switch to a more natural formatting of the macro name printing. Suggested by John McCall. llvm-svn: 142836
2011-10-25 02:51:08 +08:00
// CHECK-LIMIT: macro-backtrace.c:15:19: note: expanded from macro 'M12'
Add a prefix to the existing test to prepare for more tests of other backtrace behavior. llvm-svn: 142119
2011-10-16 15:20:23 +08:00
// CHECK-LIMIT: #define M12(A, B) M11(A, B)
Switch to a more natural formatting of the macro name printing. Suggested by John McCall. llvm-svn: 142836
2011-10-25 02:51:08 +08:00
// CHECK-LIMIT: macro-backtrace.c:14:19: note: expanded from macro 'M11'
Add a prefix to the existing test to prepare for more tests of other backtrace behavior. llvm-svn: 142119
2011-10-16 15:20:23 +08:00
// CHECK-LIMIT: #define M11(A, B) M10(A, B)
// CHECK-LIMIT: note: (skipping 7 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
Switch to a more natural formatting of the macro name printing. Suggested by John McCall. llvm-svn: 142836
2011-10-25 02:51:08 +08:00
// CHECK-LIMIT: macro-backtrace.c:6:18: note: expanded from macro 'M3'
Add a prefix to the existing test to prepare for more tests of other backtrace behavior. llvm-svn: 142119
2011-10-16 15:20:23 +08:00
// CHECK-LIMIT: #define M3(A, B) M2(A, B)
Switch to a more natural formatting of the macro name printing. Suggested by John McCall. llvm-svn: 142836
2011-10-25 02:51:08 +08:00
// CHECK-LIMIT: macro-backtrace.c:5:18: note: expanded from macro 'M2'
Add a prefix to the existing test to prepare for more tests of other backtrace behavior. llvm-svn: 142119
2011-10-16 15:20:23 +08:00
// CHECK-LIMIT: #define M2(A, B) M1(A, B)
Switch to a more natural formatting of the macro name printing. Suggested by John McCall. llvm-svn: 142836
2011-10-25 02:51:08 +08:00
// CHECK-LIMIT: macro-backtrace.c:4:23: note: expanded from macro 'M1'
Add a prefix to the existing test to prepare for more tests of other backtrace behavior. llvm-svn: 142119
2011-10-16 15:20:23 +08:00
// CHECK-LIMIT: #define M1(A, B) ((A) < (B))
Now that the structure of this is more reasonably laid out, fix a long standing deficiency: we were providing no macro backtrace information whenever caret diagnostics were turned off. This sinks the logic for suppressing the code snippet and caret to the code that actually prints tho code snippet and caret. Along the way, clean up the naming of functions, remove some now fixed FIXMEs, and generally improve the wording and logic of this process. Add a test case exerecising this functionality. It is notable that the resulting messages are extremely low quality. I'm working on a follow-up patch that should address this and have left a FIXME in the test case. llvm-svn: 142120
2011-10-16 15:20:28 +08:00
// RUN: %clang_cc1 -fsyntax-only -fno-caret-diagnostics %s 2>&1 \
// RUN: | FileCheck %s -check-prefix=CHECK-NO-CARETS
// CHECK-NO-CARETS: macro-backtrace.c:18:7: warning: comparison of distinct pointer types ('int *' and 'float *')
Switch to a more natural formatting of the macro name printing. Suggested by John McCall. llvm-svn: 142836
2011-10-25 02:51:08 +08:00
// CHECK-NO-CARETS-NEXT: macro-backtrace.c:15:19: note: expanded from macro 'M12'
// CHECK-NO-CARETS-NEXT: macro-backtrace.c:14:19: note: expanded from macro 'M11'
// CHECK-NO-CARETS-NEXT: macro-backtrace.c:13:19: note: expanded from macro 'M10'
Now that the structure of this is more reasonably laid out, fix a long standing deficiency: we were providing no macro backtrace information whenever caret diagnostics were turned off. This sinks the logic for suppressing the code snippet and caret to the code that actually prints tho code snippet and caret. Along the way, clean up the naming of functions, remove some now fixed FIXMEs, and generally improve the wording and logic of this process. Add a test case exerecising this functionality. It is notable that the resulting messages are extremely low quality. I'm working on a follow-up patch that should address this and have left a FIXME in the test case. llvm-svn: 142120
2011-10-16 15:20:28 +08:00
// CHECK-NO-CARETS-NEXT: note: (skipping 6 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
Switch to a more natural formatting of the macro name printing. Suggested by John McCall. llvm-svn: 142836
2011-10-25 02:51:08 +08:00
// CHECK-NO-CARETS-NEXT: macro-backtrace.c:6:18: note: expanded from macro 'M3'
// CHECK-NO-CARETS-NEXT: macro-backtrace.c:5:18: note: expanded from macro 'M2'
// CHECK-NO-CARETS-NEXT: macro-backtrace.c:4:23: note: expanded from macro 'M1'
Add a testcase for r142121 based on an idea from Richard Smith. Thanks! llvm-svn: 142160
2011-10-17 05:33:06 +08:00
// Check that the expansion notes respect the same formatting options as
// other diagnostics.
// RUN: %clang_cc1 -fsyntax-only -fdiagnostics-format vi %s 2>&1 \
// RUN: | FileCheck %s -check-prefix=CHECK-NOTE-FORMAT
// CHECK-NOTE-FORMAT: macro-backtrace.c +18:7: warning:
// CHECK-NOTE-FORMAT: macro-backtrace.c +15:19: note:
// CHECK-NOTE-FORMAT: macro-backtrace.c +14:19: note:
// CHECK-NOTE-FORMAT: note:
// CHECK-NOTE-FORMAT: macro-backtrace.c +6:18: note:
// CHECK-NOTE-FORMAT: macro-backtrace.c +5:18: note:
// CHECK-NOTE-FORMAT: macro-backtrace.c +4:23: note:
Introduce a limit on the depth of the macro instantiation backtrace printed in a diagnostic, similar to the limit we already have on the depth of the template instantiation backtrace. The macro instantiation backtrace is limited to 10 "instantiated from:" diagnostics; when it's longer than that, we'll show the first half, then say how many were suppressed, then show the second half. The limit can be changed with -fmacro-instantiation-limit=N, and turned off with N=0. This eliminates a lot of note spew with libraries making use of the Boost.Preprocess library. llvm-svn: 103014
2010-05-05 01:13:42 +08:00
}