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

25 lines
718 B
C
Raw Normal View History

Introduce optional "Invalid" parameters to routines that invoke the SourceManager's getBuffer() and, therefore, could fail, along with Preprocessor::getSpelling(). Use the Invalid parameters in the literal parsers (string, floating point, integral, character) to make them robust against errors that stem from, e.g., PCH files that are not consistent with the underlying file system. I still need to audit every use caller to all of these routines, to determine which ones need specific handling of error conditions. llvm-svn: 98608
2010-03-16 13:20:39 +08:00
const char *s0 = m0;
Audit all Preprocessor::getSpelling() callers, improving failure recovery for those that need it. llvm-svn: 98689
2010-03-17 06:30:13 +08:00
int s1 = m1;
Teach SourceManager's content cache to keep track of whether its buffer was invalid when it was created, and use that bit to always set the "Invalid" flag according to whether the buffer is invalid. This ensures that all accesses to an invalid buffer are marked invalid, improving recovery. llvm-svn: 98690
2010-03-17 06:53:51 +08:00
const char *s2 = m0;
Introduce optional "Invalid" parameters to routines that invoke the SourceManager's getBuffer() and, therefore, could fail, along with Preprocessor::getSpelling(). Use the Invalid parameters in the literal parsers (string, floating point, integral, character) to make them robust against errors that stem from, e.g., PCH files that are not consistent with the underlying file system. I still need to audit every use caller to all of these routines, to determine which ones need specific handling of error conditions. llvm-svn: 98608
2010-03-16 13:20:39 +08:00
XFAIL this test on that silly Windows platform. Grrr llvm-svn: 98750
2010-03-18 02:28:02 +08:00
// XFAIL: win32
Introduce optional "Invalid" parameters to routines that invoke the SourceManager's getBuffer() and, therefore, could fail, along with Preprocessor::getSpelling(). Use the Invalid parameters in the literal parsers (string, floating point, integral, character) to make them robust against errors that stem from, e.g., PCH files that are not consistent with the underlying file system. I still need to audit every use caller to all of these routines, to determine which ones need specific handling of error conditions. llvm-svn: 98608
2010-03-16 13:20:39 +08:00
// RUN: echo '#define m0 ""' > %t.h
// RUN: %clang_cc1 -emit-pch -o %t.h.pch %t.h
// RUN: echo '' > %t.h
Emit output of PCH consistency checking test case to a separate text file and grep that llvm-svn: 98695
2010-03-17 08:09:23 +08:00
// RUN: not %clang_cc1 -include-pch %t.h.pch %s 2> %t.stderr
Use a simple diagnostic (file modified) when we detect that a file has changed, rather than trying to point out how it changed. The "why" doesn't matter. llvm-svn: 98725
2010-03-17 23:30:15 +08:00
// RUN: grep "modified" %t.stderr
Introduce optional "Invalid" parameters to routines that invoke the SourceManager's getBuffer() and, therefore, could fail, along with Preprocessor::getSpelling(). Use the Invalid parameters in the literal parsers (string, floating point, integral, character) to make them robust against errors that stem from, e.g., PCH files that are not consistent with the underlying file system. I still need to audit every use caller to all of these routines, to determine which ones need specific handling of error conditions. llvm-svn: 98608
2010-03-16 13:20:39 +08:00
// RUN: echo '#define m0 000' > %t.h
// RUN: %clang_cc1 -emit-pch -o %t.h.pch %t.h
// RUN: echo '' > %t.h
Emit output of PCH consistency checking test case to a separate text file and grep that llvm-svn: 98695
2010-03-17 08:09:23 +08:00
// RUN: not %clang_cc1 -include-pch %t.h.pch %s 2> %t.stderr
Use a simple diagnostic (file modified) when we detect that a file has changed, rather than trying to point out how it changed. The "why" doesn't matter. llvm-svn: 98725
2010-03-17 23:30:15 +08:00
// RUN: grep "modified" %t.stderr
Audit all Preprocessor::getSpelling() callers, improving failure recovery for those that need it. llvm-svn: 98689
2010-03-17 06:30:13 +08:00
// RUN: echo '#define m0 000' > %t.h
// RUN: echo "#define m1 'abcd'" >> %t.h
// RUN: %clang_cc1 -emit-pch -o %t.h.pch %t.h
// RUN: echo '' > %t.h
Emit output of PCH consistency checking test case to a separate text file and grep that llvm-svn: 98695
2010-03-17 08:09:23 +08:00
// RUN: not %clang_cc1 -include-pch %t.h.pch %s 2> %t.stderr
Use a simple diagnostic (file modified) when we detect that a file has changed, rather than trying to point out how it changed. The "why" doesn't matter. llvm-svn: 98725
2010-03-17 23:30:15 +08:00
// RUN: grep "modified" %t.stderr