Changes in lookup.cpp

47972afd - [modules] Simplify -cc1 interface for enabling implicit module maps.

Tue, 16 Jun 2015 00:08:24 +0000

[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/lookup.cpp

9eb229bf - Require a module.map file to load a module

Wed, 22 Jan 2014 23:19:39 +0000

Require a module.map file to load a moduleRemoves some old code that allowed a module to be loaded from a pcm fileeven if the module.map could not be found. Also update a number oftests that relied on the old behavior.llvm-svn: 199852 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

fcc699ae - Extended VerifyDiagnosticConsumer to also verify source file for diagnostic.

Wed, 17 Apr 2013 08:06:46 +0000

Extended VerifyDiagnosticConsumer to also verify source file for diagnostic.VerifyDiagnosticConsumer previously would not check that the diagnostic andits matching directive referenced the same source file. Common practice wasto create directives that referenced other files but only by line number,and this led to problems such as when the file containing the directivedidn't have enough lines to match the location of the diagnostic in theother file, leading to bizarre file formatting and other oddities.This patch causes VerifyDiagnosticConsumer to match source files as well asline numbers. Therefore, a new syntax is made available for directives, forexample:// expected-error@file:line {{diagnostic message}}This extends the @line feature where "file" is the file where the diagnosticis generated. The @line syntax is still available and uses the current filefor the diagnostic. "file" can be specified either as a relative or absolutepath - although the latter has less usefulness, I think! The #include searchpaths will be used to locate the file and if it is not found an error will begenerated.The new check is not optional: if the directive is in a different file to thediagnostic, the file must be specified. Therefore, a number of test-caseshave been updated with regard to this.This closes out PR15613.llvm-svn: 179677 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

35b04d6f - Rename -fmodule-cache-path to -fmodules-cache-path= for consistency.

Thu, 07 Feb 2013 19:01:24 +0000

Rename -fmodule-cache-path to -fmodules-cache-path= for consistency.llvm-svn: 174645 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

c50d4924 - Use @import rather than @__experimental_modules_import, since the

Tue, 11 Dec 2012 22:11:52 +0000

Use @import rather than @__experimental_modules_import, since thelatter is rather a mess to type.llvm-svn: 169919 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

b00073db - Update VerifyDiagnosticConsumer to only get directives during parsing.

Fri, 10 Aug 2012 01:06:16 +0000

Update VerifyDiagnosticConsumer to only get directives during parsing.The old behavior was to re-scan any files (like modules) where we may havedirectives but won't actually be parsing during the -verify invocation.Now, we keep the old behavior in Debug builds as a sanity check (thoughmodules are a known entity), and expect all legitimate directives to comefrom comments seen by the preprocessor.This also affects the ARC migration tool, which captures diagnostics inorder to filter some out. This change adds an explicit cleanup toCaptureDiagnosticsConsumer in order to let its sub-consumer handle thereal end of diagnostics.This was originally split into four patches, but the tests do not runcleanly without all four, so I've combined them into one commit.Patches by Andy Gibbs, with slight modifications from me.llvm-svn: 161650 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

c1e4dd0e - Change @import to @__experimental_modules_import. We are not ready to commit to a particular syntax for modules,

Thu, 01 Mar 2012 22:07:04 +0000

Change @import to @__experimental_modules_import. We are not ready to commit to a particular syntax for modules,and don't have time to push it forward in the near future.llvm-svn: 151841 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

8d76cca3 - Don't treat 'import' as a contextual keyword when we're in a caching lexer, or when modules are disabled.

Wed, 04 Jan 2012 06:20:15 +0000

Don't treat 'import' as a contextual keyword when we're in a caching lexer, or when modules are disabled.llvm-svn: 147524 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

da82e703 - Eliminate the uglified keyword __import_module__ for importing

Tue, 03 Jan 2012 19:32:59 +0000

Eliminate the uglified keyword __import_module__ for importingmodules. This leaves us without an explicit syntax for importingmodules in C/C++, because such a syntax needs to be discussedfirst. In Objective-C/Objective-C++, the @import syntax is used toimport modules.Note that, under -fmodules, C/C++ programs can import modules via the#include mechanism when a module map is in place for that header. Thisallows us to work with modules in C/C++ without committing to a syntax.llvm-svn: 147467 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

70db54f1 - Eliminate the -emit-module option, which emitted a module by parsing a

Tue, 29 Nov 2011 22:42:06 +0000

Eliminate the -emit-module option, which emitted a module by parsing asource file (e.g., a header). Immediately steal this useful optionname for building modules from a module map file.llvm-svn: 145444 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

81ac8421 - Switch some more of the modules tests over to "-emit-module-from-map",

Wed, 16 Nov 2011 00:21:54 +0000

Switch some more of the modules tests over to "-emit-module-from-map",and remove stray fprintf.llvm-svn: 144742 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

1735f4e7 - For modules, use a hash of the compiler version, language options, and

Tue, 13 Sep 2011 23:15:45 +0000

For modules, use a hash of the compiler version, language options, andtarget triple to separate modules built under differentconditions. The hash is used to create a subdirectory in the modulecache path where other invocations of the compiler (with the sameversion, language options, etc.) can find the precompiled modules.llvm-svn: 139662 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

1e44e022 - Introduce a cc1-level option to provide the path to the module cache,

Mon, 12 Sep 2011 20:41:59 +0000

Introduce a cc1-level option to provide the path to the module cache,where the compiler will look for module files. Eliminates theegregious hack where we looked into the header search paths formodules.llvm-svn: 139538 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

ca97589f - Switch import over to __import_module__, so we don't conflict with

Wed, 31 Aug 2011 18:19:09 +0000

Switch __import__ over to __import_module__, so we don't conflict withexisting practice with Python extension modules. Not that Pythonextension modules should be using a double-underscored identifieranyway, but...llvm-svn: 138870 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

d90c3c92 - Take an entirely different approach to handling the "parsing" of

Sat, 27 Aug 2011 06:37:51 +0000

Take an entirely different approach to handling the "parsing" of__import__ within the preprocessor, since the prior one foolishlyassumed that Preprocessor::Lex() was re-entrant. We now handle__import__ at the top level (only), after macro expansion. This shouldfix the buildbot failures.llvm-svn: 138704 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

e89397ac - XFAIL one of the module tests on win32, until we figure out what's happening

Sat, 27 Aug 2011 00:29:32 +0000

XFAIL one of the module tests on win32, until we figure out what's happeningllvm-svn: 138688 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

08142534 - Introduce support for a simple module import declaration, which

Fri, 26 Aug 2011 23:56:07 +0000

Introduce support for a simple module import declaration, whichloads the named module. The syntax itself is intentionally hideous andwill be replaced at some later point with something morepalatable. For now, we're focusing on the semantics: - Module imports are handled first by the preprocessor (to get macro definitions) and then the same tokens are also handled by the parser (to get declarations). If both happen (as in normal compilation), the second one is redundant, because we currently have no way to hide macros or declarations when loading a module. Chris gets credit for this mad-but-workable scheme. - The Preprocessor now holds on to a reference to a module loader, which is responsible for loading named modules. CompilerInstance is the only important module loader: it now knows how to create and wire up an AST reader on demand to actually perform the module load. - We search for modules in the include path, using the module name with the suffix ".pcm" (precompiled module) for the file name. This is a temporary hack; we hope to improve the situation in the future.llvm-svn: 138679 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

69f74f80 - Introduce a -cc1 option "-emit-module", that creates a binary module

Thu, 25 Aug 2011 22:30:56 +0000

Introduce a -cc1 option "-emit-module", that creates a binary modulefrom the given source. -emit-module behaves similarly to -emit-pch,except that Sema is somewhat more strict about the contents of-emit-module. In the future, there are likely to be more interestingdifferences.llvm-svn: 138595 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

1257f970 - Introduce a depth-first search of modules into the module manager,

Wed, 24 Aug 2011 21:27:34 +0000

Introduce a depth-first search of modules into the module manager,which supports both pre-order and post-order traversal via a visitormechanism. Use this depth-first search with a post-order traversal togive predictable ordering semantics when walking all of the lexicaldeclarations in the translation unit.Eventually, module imports will occur in the source code rather thanat the beginning, and we'll have to revisit this walk.llvm-svn: 138490 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp

94619c81 - In the AST reader, switch name lookup within a DeclContect over to the

Wed, 24 Aug 2011 19:03:07 +0000

In the AST reader, switch name lookup within a DeclContect over to themodule DAG-based lookup scheme. This required some reshuffling, sothat each module stores its own mapping from DeclContexts to theirlexical and visible sets for those DeclContexts (rather than one big"chain"). Overall, this allows simple qualified name lookup into the translationunit to gather results from multiple modules, with the lookup resultsin module B shadowing the lookup results in module A when B imports A.Walking all of the lexical declarations in a module DAG is still amess; we'll end up walking the loaded module list backwards, whichworks fine for chained PCH but doesn't make sense in a DAG. I'lltackle this issue as a separate commit.llvm-svn: 138463 List of files: /llvm-project-15.0.7/clang/test/Modules/lookup.cpp