<?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 x86-loopvectorize-costmodel.ll.expected</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>8fbed687 - [UpdateTestChecks] Prevent rapid onset insanity when forced to write LoopVectorize-driven costmodel tests</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_analyze_test_checks/Inputs/x86-loopvectorize-costmodel.ll.expected#8fbed687</link>
        <description>[UpdateTestChecks] Prevent rapid onset insanity when forced to write LoopVectorize-driven costmodel testsSubj, or on other words, we have a lot of tests that are driven bythe LoopVectorizer&apos;s debug output, but we don&apos;t haveany meaningful way to autogenerate checklines in them,which means that an insurmountable amount of manual workis required when modifying the appropriate cost models.That is not sustainable, so this presents a solution.Reviewed By: RKSimonDifferential Revision: https://reviews.llvm.org/D121133

            List of files:
            /llvm-project-15.0.7/llvm/test/tools/UpdateTestChecks/update_analyze_test_checks/Inputs/x86-loopvectorize-costmodel.ll.expected</description>
        <pubDate>Fri, 15 Apr 2022 12:37:29 +0000</pubDate>
        <dc:creator>Roman Lebedev &lt;lebedev.ri@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
