<?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>c2132d8f - [Modules] Teach Clang to survive ambiguous macros which come from system</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Modules/Inputs/macro-ambiguity/module.modulemap#c2132d8f</link>
        <description>[Modules] Teach Clang to survive ambiguous macros which come from systemheaders even if they arrived when merging non-system modules.The idea of this code is that we don&apos;t want to warn the user aboutmacros defined multiple times by their system headers with slightlydifferent definitions. We should have this behavior if either themacro comes from a system module, or the definition within the modulecomes from a system header. Previously, we would warn on ambiguousmacros being merged when they came from a users modules even though theyonly showed up via system headers.By surviving this we can handle common system header macro differenceslike differing &apos;const&apos; qualification of pointers due to some headerspredating &apos;const&apos; being valid in C code, even when those systems headersare pre-built into a system module.Differential Revision: http://reviews.llvm.org/D8310llvm-svn: 232149

            List of files:
            /llvm-project-15.0.7/clang/test/Modules/Inputs/macro-ambiguity/module.modulemap</description>
        <pubDate>Fri, 13 Mar 2015 08:29:54 +0000</pubDate>
        <dc:creator>Chandler Carruth &lt;chandlerc@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
