bcm5719-llvm/clang/test/Modules/normal-module-map.cpp, branch meklort-10.0.1

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

2015-06-16T00:08:24+00:00

We used to have a flag to enable module maps, and two more flags to enable implicit module maps. This is all redundant; we don't need any flag for enabling 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 enables implicitly 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

During typo correction, check for an exact match in an unimported module. If we

2013-08-20T20:35:18+00:00

find one, then report the error as a missing import instead of as a typo. llvm-svn: 188821

Extended VerifyDiagnosticConsumer to also verify source file for diagnostic.

2013-04-17T08:06:46+00:00

VerifyDiagnosticConsumer previously would not check that the diagnostic and its matching directive referenced the same source file. Common practice was to create directives that referenced other files but only by line number, and this led to problems such as when the file containing the directive didn't have enough lines to match the location of the diagnostic in the other file, leading to bizarre file formatting and other oddities. This patch causes VerifyDiagnosticConsumer to match source files as well as line numbers. Therefore, a new syntax is made available for directives, for example: // expected-error@file:line {{diagnostic message}} This extends the @line feature where "file" is the file where the diagnostic is generated. The @line syntax is still available and uses the current file for the diagnostic. "file" can be specified either as a relative or absolute path - although the latter has less usefulness, I think! The #include search paths will be used to locate the file and if it is not found an error will be generated. The new check is not optional: if the directive is in a different file to the diagnostic, the file must be specified. Therefore, a number of test-cases have been updated with regard to this. This closes out PR15613. llvm-svn: 179677

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

2013-02-07T19:01:24+00:00

llvm-svn: 174645

Use @import rather than @__experimental_modules_import, since the

2012-12-11T22:11:52+00:00

latter is rather a mess to type. llvm-svn: 169919

Sanitize the names of modules determined based on the names of headers

2012-10-12T21:15:50+00:00

or directories, to make sure that they are identifiers that are not keywords in any dialect. Fixes . llvm-svn: 165821

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

2012-03-01T22:07:04+00:00

and don't have time to push it forward in the near future. llvm-svn: 151841

Eliminate the uglified keyword __import_module__ for importing

2012-01-03T19:32:59+00:00

modules. This leaves us without an explicit syntax for importing modules in C/C++, because such a syntax needs to be discussed first. In Objective-C/Objective-C++, the @import syntax is used to import 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. This allows us to work with modules in C/C++ without committing to a syntax. llvm-svn: 147467

Rename the command-line option for mapping #include/#import over to

2012-01-03T15:21:29+00:00

module imports from -fauto-module-import to -fmodules. The new name will eventually be used to enable modules, and the #include/#import mapping is a crucial part of the feature. llvm-svn: 147447

Modify how the -verify flag works. Currently, the verification string and

2011-12-15T00:38:15+00:00

diagnostic message are compared. If either is a substring of the other, then no error is given. This gives rise to an unexpected case: // expect-error{{candidate function has different number of parameters}} will match the following error messages from Clang: candidate function has different number of parameters (expected 1 but has 2) candidate function has different number of parameters It will also match these other error messages: candidate function function has different number of parameters number of parameters This patch will change so that the verification string must be a substring of the diagnostic message before accepting. Also, all the failing tests from this change have been corrected. Some stats from this cleanup: 87 - removed extra spaces around verification strings 70 - wording updates to diagnostics 40 - extra leading or trailing characters (typos, unmatched parens or quotes) 35 - diagnostic level was included (error:, warning:, or note:) 18 - flag name put in the warning (-Wprotocol) llvm-svn: 146619