<?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-ptr-is-valid.ll</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>04b944e2 - [InstSimplify] Convert tests to opaque pointers (NFC)</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Transforms/InstSimplify/null-ptr-is-valid.ll#04b944e2</link>
        <description>[InstSimplify] Convert tests to opaque pointers (NFC)The only interesting test change is in @PR31262, where the followingfold is now performed, while it previously was not:https://alive2.llvm.org/ce/z/a5Qmr6llvm/test/Transforms/InstSimplify/ConstProp/gep.ll has not beenupdated, because there is a tradeoff between folding and inrangepreservation there that we may want to discuss.Updates have been performed using:https://gist.github.com/nikic/98357b71fd67756b0f064c9517b62a34

            List of files:
            /llvm-project-15.0.7/llvm/test/Transforms/InstSimplify/null-ptr-is-valid.ll</description>
        <pubDate>Fri, 10 Jun 2022 15:07:27 +0000</pubDate>
        <dc:creator>Nikita Popov &lt;npopov@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>b280ee1d - [test] Use -passes=instsimplify instead of -instsimplify in a number of tests. NFC</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Transforms/InstSimplify/null-ptr-is-valid.ll#b280ee1d</link>
        <description>[test] Use -passes=instsimplify instead of -instsimplify in a number of tests. NFCAnother step moving away from the deprecated syntax of specifyingpass pipeline in opt.Differential Revision: https://reviews.llvm.org/D119080

            List of files:
            /llvm-project-15.0.7/llvm/test/Transforms/InstSimplify/null-ptr-is-valid.ll</description>
        <pubDate>Fri, 04 Feb 2022 10:45:19 +0000</pubDate>
        <dc:creator>Bjorn Pettersson &lt;bjorn.a.pettersson@ericsson.com&gt;</dc:creator>
    </item>
<item>
        <title>0347039a - ValueTracking: Fix isKnownNonZero for non-0 null pointers for byval</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Transforms/InstSimplify/null-ptr-is-valid.ll#0347039a</link>
        <description>ValueTracking: Fix isKnownNonZero for non-0 null pointers for byvalThe IR doesn&apos;t have a proper concept of invalid pointers, and &quot;null&quot;constants are just all zeros (though it really needs one).I think it&apos;s not possible to break this for AMDGPU due to the copysemantics of byval. If you have an original stack object at 0, thebyval copy will be placed above it so I don&apos;t think it&apos;s reallypossible to hit a 0 address.

            List of files:
            /llvm-project-15.0.7/llvm/test/Transforms/InstSimplify/null-ptr-is-valid.ll</description>
        <pubDate>Thu, 25 Jun 2020 23:12:55 +0000</pubDate>
        <dc:creator>Matt Arsenault &lt;Matthew.Arsenault@amd.com&gt;</dc:creator>
    </item>
</channel>
</rss>
