<?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 comdat-binutils.yaml</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>df8f3bf6 - [LLD] [COFF] Check the aux section definition size for IMAGE_COMDAT_SELECT_SAME_SIZE</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lld/test/COFF/Inputs/comdat-binutils.yaml#df8f3bf6</link>
        <description>[LLD] [COFF] Check the aux section definition size for IMAGE_COMDAT_SELECT_SAME_SIZEBinutils generated sections seem to be padded to a multiple of 16 bytes,but the aux section definition contains the original, unpadded sectionlength.The size check used for IMAGE_COMDAT_SELECT_SAME_SIZE previouslyonly checked the size of the section itself. When checking thecurrently processed object file against the previously chosencomdat section, we easily have access to the aux section definitionof the currently processed section, but we have to iterate over thesymbols of the previously selected object file to find the sectiondefinition of the previously picked section. (We don&apos;t want toinflate SectionChunk to carry more data, for something that is onlyneeded in corner cases.) Only do this when the mingw flag is set.This fixes statically linking clang-built C++ object files againstlibstdc++ built with GCC, if the object files contain e.g. typeinfo.Differential Revision: https://reviews.llvm.org/D86659

            List of files:
            /llvm-project-15.0.7/lld/test/COFF/Inputs/comdat-binutils.yaml</description>
        <pubDate>Wed, 26 Aug 2020 12:47:04 +0000</pubDate>
        <dc:creator>Martin Storsj&#246; &lt;martin@martin.st&gt;</dc:creator>
    </item>
</channel>
</rss>
