llvm-project

Commit Graph

Author	SHA1	Message	Date
Richard Smith	223d3f2e4d	[modules] If we import a module, and we've seen a module map that describes the module, use the path from the module map file in preference to the path from the .pcm file when resolving relative paths in the .pcm file. This allows diagnostics (and .d output) to give relative paths if the module was found via a relative path. llvm-svn: 223577	2014-12-06 03:21:08 +00:00
Richard Smith	556f03ef90	Fix module name collision in tests. llvm-svn: 195545	2013-11-23 05:21:32 +00:00
Richard Smith	34f30516aa	Generate a marker token when entering or leaving a submodule when building a module. Use the marker to diagnose cases where we try to transition between submodules when not at the top level (most likely because a closing brace was missing at the end of a header file, but is also possible if submodule headers attempt to do something fundamentally non-modular, like our .def files). llvm-svn: 195543	2013-11-23 04:06:09 +00:00

Author

SHA1

Message

Date

Richard Smith

223d3f2e4d

[modules] If we import a module, and we've seen a module map that describes the

module, use the path from the module map file in preference to the path from
the .pcm file when resolving relative paths in the .pcm file. This allows
diagnostics (and .d output) to give relative paths if the module was found via
a relative path.

llvm-svn: 223577

2014-12-06 03:21:08 +00:00

Richard Smith

556f03ef90

Fix module name collision in tests.

llvm-svn: 195545

2013-11-23 05:21:32 +00:00

Richard Smith

34f30516aa

Generate a marker token when entering or leaving a submodule when building a

module. Use the marker to diagnose cases where we try to transition between
submodules when not at the top level (most likely because a closing brace was
missing at the end of a header file, but is also possible if submodule headers
attempt to do something fundamentally non-modular, like our .def files).

llvm-svn: 195543

2013-11-23 04:06:09 +00:00

3 Commits