When inferring a submodule ID during module creation, look up the
authorDouglas Gregor <dgregor@apple.com>
Fri, 6 Jan 2012 17:19:32 +0000 (17:19 +0000)
committerDouglas Gregor <dgregor@apple.com>
Fri, 6 Jan 2012 17:19:32 +0000 (17:19 +0000)
commit224d8a74ae4087519f07479bb23de4a3ae53e24f
treef52f7d1f1c63d7f756f2920948ee6fc8090cb688
parentdc90f07b902fe9c71f4c72e8efe951d32f5c0d6d
When inferring a submodule ID during module creation, look up the
include stack to find the first file that is known to be part of the
module. This copes with situations where the module map doesn't
completely specify all of the headers that are involved in the module,
which can come up when there are very strange #include_next chains
(e.g., with weird compiler/stdlib headers like stdarg.h or float.h).

llvm-svn: 147662
clang/lib/Lex/ModuleMap.cpp
clang/test/Modules/Inputs/def-include.h [new file with mode: 0644]
clang/test/Modules/Inputs/def.h