<?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 new-dynamic-types.cpp</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>f01831eb - [analyzer] Don&apos;t crash when dynamic type of a variable is set via placement new.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/Analysis/new-dynamic-types.cpp#f01831eb</link>
        <description>[analyzer] Don&apos;t crash when dynamic type of a variable is set via placement new.If a variable or an otherwise a concrete typed-value region is beingplacement-new&apos;ed into, its dynamic type may change in arbitrary manners. Andwhen the region is used, there may be a third type that&apos;s different from boththe static and the dynamic type. It cannot be *completely* different from thedynamic type, but it may be a base class of the dynamic type - and in this casethere isn&apos;t (and shouldn&apos;t be) any indication anywhere in the AST that there isa derived-to-base cast from the dynamic type to the third type.Perform a generic cast (evalCast()) from the third type to the dynamic typein this case. From the point of view of the SVal hierarchy, this would haveproduced non-canonical SVals if we used such generic cast in the normal case,but in this case there doesn&apos;t seem to be a better option.Differential Revision: https://reviews.llvm.org/D43659llvm-svn: 326245

            List of files:
            /llvm-project-15.0.7/clang/test/Analysis/new-dynamic-types.cpp</description>
        <pubDate>Tue, 27 Feb 2018 20:54:40 +0000</pubDate>
        <dc:creator>Artem Dergachev &lt;artem.dergachev@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
