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

14 lines
436 B
C
Raw Normal View History

Fix tests that weren't actually verifying anything. Passing -verify to clang without -cc1 or -Xclang silently passes (with a printed warning, but lit doesn't care about that). This change adds -cc1 or, as is necessary in one case, -Xclang to fix this so that these tests are actually verifying as intended. I'd like to change the driver so this kind of mistake could not be made, but I'm not entirely sure how. Further, since the driver only warns about unknown flags in general, we could have similar bugs with a misspellings of arguments that would be nice to find. llvm-svn: 154776
2012-04-16 06:09:44 +08:00
// RUN: %clang_cc1 -verify -pedantic %s -fsyntax-only
attempt to fix windows testers, which generate #line by default. llvm-svn: 131882
2011-05-23 07:47:57 +08:00
// RUN: %clang_cc1 -E %s | FileCheck %s
Prior to adding the new "expected-no-diagnostics" directive to VerifyDiagnosticConsumer, make the necessary adjustment to 580 test-cases which will henceforth require this new directive. llvm-svn: 166280
2012-10-19 20:44:48 +08:00
// expected-no-diagnostics
Fix #pragma GCC system_header by making it insert a virtual linemarker into the file at the point of the pragma. This allows clang to know that all sourcelocations after the pragma are in a system header. llvm-svn: 73376
2009-06-15 13:02:34 +08:00
// rdar://6899937
#include "pragma_sysheader.h"
Invoke the FileChanged callback before pushing the linemarker for a system header. Getting it in the wrong order generated incorrect line markers in -E mode. In the testcase from PR9861 we used to generate: # 1 "test.c" 2 # 1 "./foobar.h" 1 # 0 "./foobar.h" # 0 "./foobar.h" 3 # 2 "test.c" 2 now we properly produce: # 1 "test.c" 2 # 1 "./foobar.h" 1 # 1 "./foobar.h" 3 # 2 "test.c" 2 This fixes PR9861. llvm-svn: 131871
2011-05-23 06:10:16 +08:00
// PR9861: Verify that line markers are not messed up in -E mode.
// CHECK: # 1 "{{.*}}pragma_sysheader.h" 1
Fix off-by-one error in #pragma clang system_header. The system_header pragma (from GCC) is implemented using line notes in the source manager. However, a line note's line number specifies the number not for the current line, but for the next line. This was making all line numbers appear off by one after the pragma. Reported by Andy Gibbs, uncovered during r179677. llvm-svn: 179709
2013-04-18 03:09:18 +08:00
// CHECK-NEXT: # 2 "{{.*}}pragma_sysheader.h" 3
Invoke the FileChanged callback before pushing the linemarker for a system header. Getting it in the wrong order generated incorrect line markers in -E mode. In the testcase from PR9861 we used to generate: # 1 "test.c" 2 # 1 "./foobar.h" 1 # 0 "./foobar.h" # 0 "./foobar.h" 3 # 2 "test.c" 2 now we properly produce: # 1 "test.c" 2 # 1 "./foobar.h" 1 # 1 "./foobar.h" 3 # 2 "test.c" 2 This fixes PR9861. llvm-svn: 131871
2011-05-23 06:10:16 +08:00
// CHECK-NEXT: typedef int x;
// CHECK-NEXT: typedef int x;
Prior to adding the new "expected-no-diagnostics" directive to VerifyDiagnosticConsumer, make the necessary adjustment to 580 test-cases which will henceforth require this new directive. llvm-svn: 166280
2012-10-19 20:44:48 +08:00
// CHECK-NEXT: # 6 "{{.*}}pragma_sysheader.c" 2