<?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 chain-conversion-lookup.cpp</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>3b65ed0a - Change the hashing function for DeclContext lookup within an AST file</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/PCH/chain-conversion-lookup.cpp#3b65ed0a</link>
        <description>Change the hashing function for DeclContext lookup within an AST fileby eliminating the type ID from constructor, destructor, andconversion function names. There are several reasons for this change:  - A given type (say, int*) isn&apos;t guaranteed to have a single, unique  type ID within a chain of PCH files. Hence, we could end up hashing  based on the wrong type ID, causing name lookup to fail.  - The mapping from types back to type IDs required one DenseMap  entry for every type that was ever deserialized, which was an  unacceptable cost to support just the name lookup of constructors,  destructors, and conversion functions. Plus, this mapping could  never actually work with chained or multiple PCH, based on the first  bullet.Once we have eliminated the type from the hash function, theseproblems go away, as does my horrible &quot;reverse type remap&quot; hack, whichwas doomed from the start (see bullet #1 above) and far toocomplicated. However, note that removing the type from the hash function means thatall constructors, destructors, and conversion functions have the samehash key, so I&apos;ve updated the caller to double-check that thedeclarations found have the appropriate name.llvm-svn: 136708

            List of files:
            /llvm-project-15.0.7/clang/test/PCH/chain-conversion-lookup.cpp</description>
        <pubDate>Tue, 02 Aug 2011 18:32:54 +0000</pubDate>
        <dc:creator>Douglas Gregor &lt;dgregor@apple.com&gt;</dc:creator>
    </item>
</channel>
</rss>
