llvm-project/clang/test/Preprocessor/pp-record.c

// RUN: %clang_cc1 -fsyntax-only -detailed-preprocessing-record %s

// http://llvm.org/PR11120

#define STRINGIZE(text) STRINGIZE_I(text)
#define STRINGIZE_I(text) #text

#define INC pp-record.h

#include STRINGIZE(INC)

CAKE;

#define DIR 1
#define FNM(x) x

FNM(
#if DIR
    int a;
#else
    int b;
#endif
)

#define M1 c
#define M2 int
#define FM2(x,y) y x
FM2(M1, M2);

#define FM3(x) x
FM3(
#define M3 int x2
)
M3;
Handle the case where preprocessor entities are not received in order, fixes http://llvm.org/PR11120 llvm-svn: 141788 2011-10-13 01:36:33 +08:00			`// RUN: %clang_cc1 -fsyntax-only -detailed-preprocessing-record %s`

			`// http://llvm.org/PR11120`

[preprocessor] Handle correctly inclusion directives that have macro expansions, e.g "#include MACRO(STUFF)". -As an inclusion position for the included file, use the file location of the file where it was included but after the macro expansions. We want the macro expansions to be considered as before-in-translation-unit for everything in the included file. -In the preprocessing record take into account that only inclusion directives can be encountered as "out-of-order" (by comparing the start of the range which for inclusions is the hash location) and use binary search if there is an extreme number of macro expansions in the include directive. Fixes rdar://11111779 llvm-svn: 153527 2012-03-28 02:47:48 +08:00			`#define STRINGIZE(text) STRINGIZE_I(text)`
			`#define STRINGIZE_I(text) #text`
Handle the case where preprocessor entities are not received in order, fixes http://llvm.org/PR11120 llvm-svn: 141788 2011-10-13 01:36:33 +08:00
[preprocessor] Handle correctly inclusion directives that have macro expansions, e.g "#include MACRO(STUFF)". -As an inclusion position for the included file, use the file location of the file where it was included but after the macro expansions. We want the macro expansions to be considered as before-in-translation-unit for everything in the included file. -In the preprocessing record take into account that only inclusion directives can be encountered as "out-of-order" (by comparing the start of the range which for inclusions is the hash location) and use binary search if there is an extreme number of macro expansions in the include directive. Fixes rdar://11111779 llvm-svn: 153527 2012-03-28 02:47:48 +08:00			`#define INC pp-record.h`

			`#include STRINGIZE(INC)`

			`CAKE;`
[preprocessor] Make sure that MacroExpands callbacks are always in source order. Fixes assertion hit in the preprocessing record. rdar://11426523 llvm-svn: 156557 2012-05-11 02:57:19 +08:00
			`#define DIR 1`
			`#define FNM(x) x`

			`FNM(`
			`#if DIR`
			`int a;`
			`#else`
			`int b;`
			`#endif`
			`)`
[PreprocessingRecord] A macro expansion can be reported out-of-order in cases when there are macro expansions inside macro arguments where the arguments are not expanded in the same order as listed; don't assert that all macro expansions are in source order. rdar://12397063 llvm-svn: 172018 2013-01-10 07:22:20 +08:00
			`#define M1 c`
			`#define M2 int`
			`#define FM2(x,y) y x`
			`FM2(M1, M2);`
[preprocessing record] Have the MacroDefinitions map point to the MacroDefinition object instead its index in the preprocessed entities vector. This is because the order of the entities in the vector can change in some (uncommon) cases. llvm-svn: 175907 2013-02-23 02:35:59 +08:00
			`#define FM3(x) x`
			`FM3(`
			`#define M3 int x2`
			`)`
			`M3;`