<?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 warn-vla.cpp</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>f7f2e426 - PR47805: Use a single object for a function parameter in the caller and</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp#f7f2e426</link>
        <description>PR47805: Use a single object for a function parameter in the caller andcallee in constant evaluation.We previously made a deep copy of function parameters of class type whenpassing them, resulting in the destructor for the parameter applying tothe original argument value, ignoring any modifications made in thefunction body. This also meant that the &apos;this&apos; pointer of the functionparameter could be observed changing between the caller and the callee.This change completely reimplements how we model function parametersduring constant evaluation. We now model them roughly as if they werevariables living in the caller, albeit with an artificially reducedscope that covers only the duration of the function call, instead ofmodeling them as temporaries in the caller that we partially &quot;reparent&quot;into the callee at the point of the call. This brings some minordiagnostic improvements, as well as significantly reduced stack usageduring constant evaluation.

            List of files:
            /llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp</description>
        <pubDate>Tue, 13 Oct 2020 17:03:02 +0000</pubDate>
        <dc:creator>Richard Smith &lt;richard@metafoo.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>69f7c006 - Revert &quot;PR47805: Use a single object for a function parameter in the caller and&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp#69f7c006</link>
        <description>Revert &quot;PR47805: Use a single object for a function parameter in the caller and&quot;Breaks a clangd unit test.This reverts commit 8f8b9f2cca0b73314342c721186ae9c860ca273c.

            List of files:
            /llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp</description>
        <pubDate>Wed, 14 Oct 2020 02:31:41 +0000</pubDate>
        <dc:creator>Richard Smith &lt;richard@metafoo.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>8f8b9f2c - PR47805: Use a single object for a function parameter in the caller and</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp#8f8b9f2c</link>
        <description>PR47805: Use a single object for a function parameter in the caller andcallee in constant evaluation.We previously made a deep copy of function parameters of class type whenpassing them, resulting in the destructor for the parameter applying tothe original argument value, ignoring any modifications made in thefunction body. This also meant that the &apos;this&apos; pointer of the functionparameter could be observed changing between the caller and the callee.This change completely reimplements how we model function parametersduring constant evaluation. We now model them roughly as if they werevariables living in the caller, albeit with an artificially reducedscope that covers only the duration of the function call, instead ofmodeling them as temporaries in the caller that we partially &quot;reparent&quot;into the callee at the point of the call. This brings some minordiagnostic improvements, as well as significantly reduced stack usageduring constant evaluation.

            List of files:
            /llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp</description>
        <pubDate>Tue, 13 Oct 2020 17:03:02 +0000</pubDate>
        <dc:creator>Richard Smith &lt;richard@metafoo.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>ab870f30 - Revert &quot;PR47805: Use a single object for a function parameter in the caller and&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp#ab870f30</link>
        <description>Revert &quot;PR47805: Use a single object for a function parameter in the caller and&quot;The buildbots are displeased.This reverts commit 8d03a972ce8e92815ffe3d5d86aa027605ed92e2.

            List of files:
            /llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp</description>
        <pubDate>Tue, 13 Oct 2020 22:59:00 +0000</pubDate>
        <dc:creator>Richard Smith &lt;richard@metafoo.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>8d03a972 - PR47805: Use a single object for a function parameter in the caller and</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp#8d03a972</link>
        <description>PR47805: Use a single object for a function parameter in the caller andcallee in constant evaluation.We previously made a deep copy of function parameters of class type whenpassing them, resulting in the destructor for the parameter applying tothe original argument value, ignoring any modifications made in thefunction body. This also meant that the &apos;this&apos; pointer of the functionparameter could be observed changing between the caller and the callee.This change completely reimplements how we model function parametersduring constant evaluation. We now model them roughly as if they werevariables living in the caller, albeit with an artificially reducedscope that covers only the duration of the function call, instead ofmodeling them as temporaries in the caller that we partially &quot;reparent&quot;into the callee at the point of the call. This brings some minordiagnostic improvements, as well as significantly reduced stack usageduring constant evaluation.

            List of files:
            /llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp</description>
        <pubDate>Tue, 13 Oct 2020 17:03:02 +0000</pubDate>
        <dc:creator>Richard Smith &lt;richard@metafoo.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>6f339367 - Explain why the array bound is non-constant in VLA diagnostics.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp#6f339367</link>
        <description>Explain why the array bound is non-constant in VLA diagnostics.In passing, also use a more precise diagnostic to explain why anexpression is not an ICE if it&apos;s not of integral type.

            List of files:
            /llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp</description>
        <pubDate>Wed, 19 Aug 2020 19:46:22 +0000</pubDate>
        <dc:creator>Richard Smith &lt;richard@metafoo.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>6c926ccb - Implement -Wvla correctly</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp#6c926ccb</link>
        <description>Implement -Wvla correctlyGCC implements -Wvla as &quot;warn on every VLA&quot; (this is useful to find every VLA,for example, if they are forbidden by coding guidelines).  Currently Clangimplements -Wvla as &quot;warn on VLA when it is an extension&quot;.The attached patch makes our behavior match GCC.  The existing vla extwarn ismoved under -Wvla-extension and is still included into -Wgnu.This fixes PR5953.llvm-svn: 173286

            List of files:
            /llvm-project-15.0.7/clang/test/SemaCXX/warn-vla.cpp</description>
        <pubDate>Wed, 23 Jan 2013 20:02:51 +0000</pubDate>
        <dc:creator>Dmitri Gribenko &lt;gribozavr@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
