summaryrefslogtreecommitdiffstats
path: root/llvm/lib/DebugInfo/PDB/Native/ModuleDebugStream.cpp
diff options
context:
space:
mode:
authorRichard Smith <richard-llvm@metafoo.co.uk>2017-04-29 00:34:47 +0000
committerRichard Smith <richard-llvm@metafoo.co.uk>2017-04-29 00:34:47 +0000
commitc51c38b4ec63ca17f5d38ec73b218a0247b39ace (patch)
treea2c3032fc1feb995c824e078a39c82086319a6d1 /llvm/lib/DebugInfo/PDB/Native/ModuleDebugStream.cpp
parent6fdcb3c2cea9af306285867f4b4132e4149af8a6 (diff)
downloadbcm5719-llvm-c51c38b4ec63ca17f5d38ec73b218a0247b39ace.tar.gz
bcm5719-llvm-c51c38b4ec63ca17f5d38ec73b218a0247b39ace.zip
Add pragma to perform module import and use it in -E output.
Many of our supported configurations support modules but do not have any first-class syntax to perform a module import. This leaves us with a problem: there is no way to represent the expansion of a #include that imports a module in the -E output for such languages. (We don't want to just leave it as a #include because that requires the consumer of the preprocessed source to have the same file system layout and include paths as the creator.) This patch adds a new pragma: #pragma clang module import MODULE.NAME.HERE that imports a module, and changes -E and -frewrite-includes to use it when rewriting a #include that maps to a module import. We don't make any attempt to use a native language syntax import if one exists, to get more consistent output. (If in the future, @import and #include have different semantics in some way, the pragma will track the #include semantics.) llvm-svn: 301725
Diffstat (limited to 'llvm/lib/DebugInfo/PDB/Native/ModuleDebugStream.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud