<?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>57721ac5 - [modules] Fix some of the confusion when computing the override set for a macro</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/macro-hiding/module.modulemap#57721ac5</link>
        <description>[modules] Fix some of the confusion when computing the override set for a macrointroduced by finalization. This is still not entirely correct; more fixes tofollow.llvm-svn: 213498

            List of files:
            /llvm-project-15.0.7/clang/test/Modules/Inputs/macro-hiding/module.modulemap</description>
        <pubDate>Mon, 21 Jul 2014 04:10:40 +0000</pubDate>
        <dc:creator>Richard Smith &lt;richard-llvm@metafoo.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>e657bbdc - Reinstate r213348, reverted in r213395, with an additional bug fix and more</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/macro-hiding/module.modulemap#e657bbdc</link>
        <description>Reinstate r213348, reverted in r213395, with an additional bug fix and morethorough tests.Original commit message:[modules] Fix macro hiding bug exposed if: * A submodule of module A is imported into module B * Another submodule of module A that is not imported into B exports a macro * Some submodule of module B also exports a definition of the macro, and   happens to be the first submodule of B that imports module A.In this case, we would incorrectly determine that A&apos;s macro redefines B&apos;smacro, and so we don&apos;t need to re-export B&apos;s macro at all.This happens with the &apos;assert&apos; macro in an LLVM self-host. =(llvm-svn: 213416

            List of files:
            /llvm-project-15.0.7/clang/test/Modules/Inputs/macro-hiding/module.modulemap</description>
        <pubDate>Fri, 18 Jul 2014 22:13:40 +0000</pubDate>
        <dc:creator>Richard Smith &lt;richard-llvm@metafoo.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>3965412f - [modules] Fix macro hiding bug exposed if:</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/macro-hiding/module.modulemap#3965412f</link>
        <description>[modules] Fix macro hiding bug exposed if: * A submodule of module A is imported into module B * Another submodule of module A that is not imported into B exports a macro * Some submodule of module B also exports a definition of the macro, and   happens to be the first submodule of B that imports module A.In this case, we would incorrectly determine that A&apos;s macro redefines B&apos;smacro, and so we don&apos;t need to re-export B&apos;s macro at all.This happens with the &apos;assert&apos; macro in an LLVM self-host. =(llvm-svn: 213348

            List of files:
            /llvm-project-15.0.7/clang/test/Modules/Inputs/macro-hiding/module.modulemap</description>
        <pubDate>Fri, 18 Jul 2014 04:53:37 +0000</pubDate>
        <dc:creator>Richard Smith &lt;richard-llvm@metafoo.co.uk&gt;</dc:creator>
    </item>
</channel>
</rss>
