en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/modular_maps/modulea.map#34dc4811 Revert "Modules: Make missing headers in a module.map a warning not an error."This was committed accidentally.llvm-svn: 197389 List of files: /llvm-project-15.0.7/clang/test/Modules/Inputs/modular_maps/modulea.map Mon, 16 Dec 2013 14:57:22 +0000 Daniel Jasper <djasper@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/modular_maps/modulea.map#5c6ee49f Modules: Make missing headers in a module.map a warning not an error.Instead, mark the module as unavailable so that clang errors as soon assomeone tries to build this module.A better long-term strategy might be to not stat the header files at allwhile reading the module map and instead read them only when the moduleis being built (there is a corresponding FIXME in parseHeaderDecl()).However, it seems non-trivial to get there and this would be a temporarysolution to unblock us.Also changed the implementation to reuse the same DiagnosticsEngine asotherwise warnings can't be enabled or disabled with command-line flags.llvm-svn: 197388 List of files: /llvm-project-15.0.7/clang/test/Modules/Inputs/modular_maps/modulea.map Mon, 16 Dec 2013 14:53:57 +0000 Daniel Jasper <djasper@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/modular_maps/modulea.map#97da9178 Allow a header to be part of multiple modules.This patch changes two things:a) Allow a header to be part of multiple modules. The reasoning is thatin existing codebases that have a module-like build system, the sameheaders might be used in several build targets. Simple reasons might bethat they defined different classes that are declared in the sameheader. Supporting a header as a part of multiple modules will make thetransistion easier for those cases. A later step in clang can thendetermine whether the two modules are actually compatible and can bemerged and error out appropriately. The later check is similar to whatneeds to be done for template specializations anyway.b) Allow modules to be stored in a directory tree separate from theheaders they describe.Review: http://llvm-reviews.chandlerc.com/D1951llvm-svn: 193151 List of files: /llvm-project-15.0.7/clang/test/Modules/Inputs/modular_maps/modulea.map Tue, 22 Oct 2013 08:09:47 +0000 Daniel Jasper <djasper@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/modular_maps/modulea.map#ca9f7381 Add -fmodule-map-file option.With this option, arbitrarily named module map files can be specifiedto be loaded as required for headers in the respective (sub)directories.This, together with the extern module declaration allows for specifyingmodule maps in a modular fashion without the need for files called"module.map".Among other things, this allows a directory to contain two modules thatare completely independent of one another.Review: http://llvm-reviews.chandlerc.com/D1697.llvm-svn: 191284 List of files: /llvm-project-15.0.7/clang/test/Modules/Inputs/modular_maps/modulea.map Tue, 24 Sep 2013 09:27:13 +0000 Daniel Jasper <djasper@google.com>