llvm-project

Commit Graph

Author	SHA1	Message	Date
Richard Smith	a21c8e14b6	When preprocessing with -frewrite-imports and -fmodule-file=, do not pass all modules to preprocessing of nested .pcm files. Making those module files available results in loading more .pcm files than necessary, and potentially in misbehavior if a module makes itself visible during its own compilation (as parts of that module that have not yet been processed would then become visible). llvm-svn: 306320	2017-06-26 19:39:25 +00:00
Richard Smith	4eca9b9372	[modules] When using -E, we may try to merge decls despite having no Sema object. In such a case, use the TU's DC for merging global decls rather than giving up when we find there is no TU scope. Ultimately, we should probably avoid all loading of decls when preprocessing, but there are other reasonable use cases for loading an AST file with no Sema object for which this is the right thing. llvm-svn: 228234	2015-02-04 23:37:59 +00:00

Author

SHA1

Message

Date

Richard Smith

a21c8e14b6

When preprocessing with -frewrite-imports and -fmodule-file=, do not pass all

modules to preprocessing of nested .pcm files.

Making those module files available results in loading more .pcm files than
necessary, and potentially in misbehavior if a module makes itself visible
during its own compilation (as parts of that module that have not yet been
processed would then become visible).

llvm-svn: 306320

2017-06-26 19:39:25 +00:00

Richard Smith

4eca9b9372

[modules] When using -E, we may try to merge decls despite having no Sema

object. In such a case, use the TU's DC for merging global decls rather than
giving up when we find there is no TU scope.

Ultimately, we should probably avoid all loading of decls when preprocessing,
but there are other reasonable use cases for loading an AST file with no Sema
object for which this is the right thing.

llvm-svn: 228234

2015-02-04 23:37:59 +00:00

2 Commits