llvm-project/clang/test/Modules/Inputs/va_list/module.modulemap

module va_list_a { header "va_list_a.h" }
module va_list_b { header "va_list_b.h" }
module top { header "top.h" }
module left { header "left.h" }
module right { header "right.h" }
Move the initialization of VAListTagName after InitializeSema() This innocuous statement to get the identifier info for __va_list_tag was causing an assertion failure: NextIsPrevious() && "decl became non-canonical unexpectedly" if the __va_list_tag identifier was found in a PCH in some circumstances, because it was looked up before the ASTReader had a Sema object to use to find existing decls to merge with. We could possibly move getting the identifier info even later, or make it lazy if we wanted to, but this seemed like the minimal change. Now why a PCH would have this identifier in the first place is a bit mysterious. This seems to be related to the global module index in some way, because when the test case is built without the global module index it will not emit an identifier for __va_list_tag into the PCH, but with the global module index it does. llvm-svn: 217275 2014-09-06 04:24:27 +08:00			`module va_list_a { header "va_list_a.h" }`
			`module va_list_b { header "va_list_b.h" }`
[modules] Fix merging of __va_list_tag's implicit special member functions. We model predefined declarations as not being from AST files, but in most ways they act as if they come from some implicit prebuilt module file imported before all others. Therefore, if we see an update to the predefined 'struct __va_list_tag' declaration (and we've already loaded any modules), it needs a corresponding update record, even though it didn't technically come from an AST file. llvm-svn: 250134 2015-10-13 08:23:25 +08:00			`module top { header "top.h" }`
			`module left { header "left.h" }`
			`module right { header "right.h" }`