llvm-project/clang/test/PCH/Inputs/chain-macro-override1.h

void f() __attribute__((unavailable));
void g();
#define g() f()
#define h() f()
#define x x
#define h2() f()

#define h3()
#undef h3
Make macro weirdness in chained PCH work. This required changing the way PCHReader and PCHWriter are initialized to correctly pick up all initializer. On the upside, this means that there is far less repetition in the dependent PCH now. llvm-svn: 109823 2010-07-30 08:29:29 +08:00			`void f() __attribute__((unavailable));`
			`void g();`
			`#define g() f()`
			`#define h() f()`
When an identifier that has a macro definition in the original PCH file is somehow changed in a chained PCH file, make sure that we write out the macro definition. Fixes part of <rdar://problem/8499034>. llvm-svn: 115259 2010-10-01 09:03:07 +08:00			`#define x x`
Rework the (de-)serialization of macros, as stored in MacroInfo*. Instead of simply dumping an offset into the current file, give each macro definition a proper ID with all of the standard modules-remapping facilities. Additionally, when a macro is modified in a subsequent AST file (e.g., #undef'ing a macro loaded from another module or from a precompiled header), provide a macro update record rather than rewriting the entire macro definition. This gives us greater consistency with the way we handle declarations, and ties together macro definitions much more cleanly. Note that we're still not actually deserializing macro history (we never were), but it's far easy to do properly now. llvm-svn: 165560 2012-10-10 07:05:51 +08:00			`#define h2() f()`

			`#define h3()`
			`#undef h3`