<?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 null_schedule.ll</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>5c028081 - [polly] Introduce -polly-print-* passes to replace -analyze.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll#5c028081</link>
        <description>[polly] Introduce -polly-print-* passes to replace -analyze.The `opt -analyze` option only works with the legacy pass manager and might be removed in the future, as explained in llvm.org/PR53733. This patch introduced -polly-print-* passes that print what the pass would print with the `-analyze` option and replaces all uses of `-analyze` in the regression tests.There are two exceptions: `CodeGen\single_loop_param_less_equal.ll` and `CodeGen\loop_with_condition_nested.ll` use `-analyze on the `-loops` pass which is not part of Polly.Reviewed By: aeubanksDifferential Revision: https://reviews.llvm.org/D120782

            List of files:
            /llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll</description>
        <pubDate>Mon, 14 Mar 2022 13:39:25 +0000</pubDate>
        <dc:creator>Michael Kruse &lt;llvm-project@meinersbur.de&gt;</dc:creator>
    </item>
<item>
        <title>b210c989 - [BasicAA] Replace -basicaa with -basic-aa in polly</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll#b210c989</link>
        <description>[BasicAA] Replace -basicaa with -basic-aa in pollyFollow up to https://reviews.llvm.org/D82607.

            List of files:
            /llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll</description>
        <pubDate>Tue, 30 Jun 2020 22:40:24 +0000</pubDate>
        <dc:creator>Arthur Eubanks &lt;aeubanks@google.com&gt;</dc:creator>
    </item>
<item>
        <title>f4ee371e - tests: Drop -polly-detect-unprofitable and -polly-no-early-exit</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll#f4ee371e</link>
        <description>tests: Drop -polly-detect-unprofitable and -polly-no-early-exitThese flags are now always passed to all tests and need to be disabled ifnot needed. Disabling these flags, rather than passing them to almost alltests, significantly simplfies our RUN: lines.llvm-svn: 249422

            List of files:
            /llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll</description>
        <pubDate>Tue, 06 Oct 2015 15:36:44 +0000</pubDate>
        <dc:creator>Tobias Grosser &lt;tobias@grosser.es&gt;</dc:creator>
    </item>
<item>
        <title>808cd69a - Use schedule trees to represent execution order of statements</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll#808cd69a</link>
        <description>Use schedule trees to represent execution order of statementsInstead of flat schedules, we now use so-called schedule trees to represent theexecution order of the statements in a SCoP. Schedule trees make it a lot easierto analyze, understand and modify properties of a schedule, as specific nodesin the tree can be choosen and possibly replaced.This patch does not yet fully move our DependenceInfo pass to schedule trees,as some additional performance analysis is needed here. (In general scheduletrees should be faster in compile-time, as the more structured representationis generally easier to analyze and work with). We also can not yet perform thereduction analysis on schedule trees.For more information regarding schedule trees, please see Section 6 ofhttps://lirias.kuleuven.be/handle/123456789/497238llvm-svn: 242130

            List of files:
            /llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll</description>
        <pubDate>Tue, 14 Jul 2015 09:33:13 +0000</pubDate>
        <dc:creator>Tobias Grosser &lt;tobias@grosser.es&gt;</dc:creator>
    </item>
<item>
        <title>173ecab7 - Remove target triples from test cases</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll#173ecab7</link>
        <description>Remove target triples from test casesI just learned that target triples prevent test cases to be run on otherarchitectures. Polly test cases are until now sufficiently target independentto not require any target triples. Hence, we drop them.llvm-svn: 235384

            List of files:
            /llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll</description>
        <pubDate>Tue, 21 Apr 2015 14:28:02 +0000</pubDate>
        <dc:creator>Tobias Grosser &lt;tobias@grosser.es&gt;</dc:creator>
    </item>
<item>
        <title>c94eca05 - Update Polly tests to handle explicitly typed load changes in LLVM.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll#c94eca05</link>
        <description>Update Polly tests to handle explicitly typed load changes in LLVM.llvm-svn: 230796

            List of files:
            /llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll</description>
        <pubDate>Fri, 27 Feb 2015 21:22:50 +0000</pubDate>
        <dc:creator>David Blaikie &lt;dblaikie@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>bad3ff20 - Update Polly tests to handle explicitly typed gep changes in LLVM</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll#bad3ff20</link>
        <description>Update Polly tests to handle explicitly typed gep changes in LLVMllvm-svn: 230784

            List of files:
            /llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll</description>
        <pubDate>Fri, 27 Feb 2015 19:20:19 +0000</pubDate>
        <dc:creator>David Blaikie &lt;dblaikie@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d1e33e70 - ScopDetection: Only detect scops that have at least one read and one write</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll#d1e33e70</link>
        <description>ScopDetection: Only detect scops that have at least one read and one writeScops that only read seem generally uninteresting and scops that only write aremost likely initializations where there is also little to optimize.  To notwaste compile time we bail early.Differential Revision: http://reviews.llvm.org/D7735llvm-svn: 229820

            List of files:
            /llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll</description>
        <pubDate>Thu, 19 Feb 2015 05:31:07 +0000</pubDate>
        <dc:creator>Tobias Grosser &lt;tobias@grosser.es&gt;</dc:creator>
    </item>
<item>
        <title>7ceb0402 - Add early exits for SCoPs we did not optimize</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll#7ceb0402</link>
        <description>Add early exits for SCoPs we did not optimize  This allows us to skip ast and code generation if we did not optimize  a SCoP and will not generate parallel or alias annotations. The  initial heuristic to exit is simple but allows improvements later on.  All failing test cases have been modified to disable early exit, thus  to keep their coverage.  Differential Revision: http://reviews.llvm.org/D7254llvm-svn: 228851

            List of files:
            /llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll</description>
        <pubDate>Wed, 11 Feb 2015 17:25:09 +0000</pubDate>
        <dc:creator>Johannes Doerfert &lt;doerfert@cs.uni-saarland.de&gt;</dc:creator>
    </item>
<item>
        <title>37eb422f - Add polyhedral dead code elimination.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll#37eb422f</link>
        <description>Add polyhedral dead code elimination.This pass eliminates loop iterations that compute results that are not usedlater on. This can help e.g. in D, where the default zero-initialization isoften unnecessary if right after new values are assigned to an array.Contributed-by: Peter Conn &lt;conn.peter@gmail.com&gt;llvm-svn: 201817

            List of files:
            /llvm-project-15.0.7/polly/test/DeadCodeElimination/null_schedule.ll</description>
        <pubDate>Thu, 20 Feb 2014 21:43:54 +0000</pubDate>
        <dc:creator>Tobias Grosser &lt;tobias@grosser.es&gt;</dc:creator>
    </item>
</channel>
</rss>
