<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in module.modulemap</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>ffd3e9d7 - PCH: fix a regression that reports a module is defined in both pch and pcm.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/pch-with-module-name/module.modulemap#ffd3e9d7</link>
        <description>PCH: fix a regression that reports a module is defined in both pch and pcm.In r276159, we started to say that a module X is defined in a pch if we specify-fmodule-name when building the pch. This caused a regression that reportsmodule X is defined in both pch and pcm if we generate the pch with-fmodule-name=X and then in a separate clang invocation, we include the pch andalso import X.pcm.This patch adds an option CompilingPCH similar to CompilingModule. When we use-fmodule-name=X while building a pch, modular headers in X will be textuallyincluded and the compiler knows that we are not building module X, so we don&apos;tput module X in SUBMODULE_DEFINITION of the pch.Differential Revision: http://reviews.llvm.org/D28415llvm-svn: 291465

            List of files:
            /llvm-project-15.0.7/clang/test/Modules/Inputs/pch-with-module-name/module.modulemap</description>
        <pubDate>Mon, 09 Jan 2017 19:20:18 +0000</pubDate>
        <dc:creator>Manman Ren &lt;manman.ren@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
