<?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 Polly.cpp</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>24ab9b53 - Generalize the pass registration mechanism used by Polly to any third-party tool</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/lib/Plugin/Polly.cpp#24ab9b53</link>
        <description>Generalize the pass registration mechanism used by Polly to any third-party toolThere&apos;s quite a lot of references to Polly in the LLVM CMake codebase. Howeverthe registration pattern used by Polly could be useful to other externalprojects: thanks to that mechanism it would be possible to develop LLVMextension without touching the LLVM code base.This patch has two effects:1. Remove all code specific to Polly in the llvm/clang codebase, replaicing it   with a generic mechanism2. Provide a generic mechanism to register compiler extensions.A compiler extension is similar to a pass plugin, with the notable differencethat the compiler extension can be configured to be built dynamically (likeplugins) or statically (like regular passes).As a result, people willing to add extra passes to clang/opt can do it using aseparate code repo, but still have their pass be linked in clang/opt as built-inpasses.Differential Revision: https://reviews.llvm.org/D61446

            List of files:
            /llvm-project-15.0.7/polly/lib/Plugin/Polly.cpp</description>
        <pubDate>Sat, 08 Jun 2019 15:37:47 +0000</pubDate>
        <dc:creator>serge_sans_paille &lt;sguelton@redhat.com&gt;</dc:creator>
    </item>
</channel>
</rss>
