en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/macro-ambiguity.cpp#47972afd [modules] Simplify -cc1 interface for enabling implicit module maps.We used to have a flag to enable module maps, and two more flags to enableimplicit module maps. This is all redundant; we don't need any flag forenabling module maps in the abstract, and we don't usually have -fno- flags for-cc1. We now have just a single flag, -fimplicit-module-maps, that enablesimplicitly searching the file system for module map files and loading them.The driver interface is unchanged for now. We should probably rename-fmodule-maps to -fimplicit-module-maps at some point.llvm-svn: 239789 List of files: /llvm-project-15.0.7/clang/test/Modules/macro-ambiguity.cpp Tue, 16 Jun 2015 00:08:24 +0000 Richard Smith <richard-llvm@metafoo.co.uk> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/macro-ambiguity.cpp#ee977933 [modules] Add -fmodules-local-submodule-visibility flag.This flag specifies that the normal visibility rules should be used even forlocal submodules (submodules of the currently-being-built module). Thus nameswill only be visible if a header / module that declares them has actually beenincluded / imported, and not merely because a submodule that happened to bebuilt earlier declared those names. This also removes the need to modularizebottom-up: textually-included headers will be included into every submodulethat includes them, since their include guards will not leak between modules.So far, this only governs visibility of macros, not of declarations, so is notready for real use yet.llvm-svn: 236350 List of files: /llvm-project-15.0.7/clang/test/Modules/macro-ambiguity.cpp Fri, 01 May 2015 21:22:17 +0000 Richard Smith <richard-llvm@metafoo.co.uk> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/macro-ambiguity.cpp#c2132d8f [Modules] Teach Clang to survive ambiguous macros which come from systemheaders even if they arrived when merging non-system modules.The idea of this code is that we don't want to warn the user aboutmacros defined multiple times by their system headers with slightlydifferent definitions. We should have this behavior if either themacro comes from a system module, or the definition within the modulecomes from a system header. Previously, we would warn on ambiguousmacros being merged when they came from a users modules even though theyonly showed up via system headers.By surviving this we can handle common system header macro differenceslike differing 'const' qualification of pointers due to some headerspredating 'const' being valid in C code, even when those systems headersare pre-built into a system module.Differential Revision: http://reviews.llvm.org/D8310llvm-svn: 232149 List of files: /llvm-project-15.0.7/clang/test/Modules/macro-ambiguity.cpp Fri, 13 Mar 2015 08:29:54 +0000 Chandler Carruth <chandlerc@gmail.com>