<?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 gnu-implib-func.s</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>5f6d527f - [COFF] Support linking to import libraries from GNU binutils</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lld/test/COFF/Inputs/gnu-implib-func.s#5f6d527f</link>
        <description>[COFF] Support linking to import libraries from GNU binutilsGNU binutils import libraries aren&apos;t the same kind of short importlibraries as link.exe and LLD produce, but are a plain static librarycontaining .idata section chunks. MSVC link.exe can successfully linkto them.In order for imports from GNU import libraries to mix properly with thenormal import chunks, the chunks from the existing mechanism needs tobe added into named sections like .idata$2.These GNU import libraries consist of one header object, a number ofobject files, one for each imported function/variable, and one trailer.Within the import libraries, the object files are ordered alphabeticallyin this order. The chunks stemming from these libraries have to begrouped by what library they originate from and sorted, to make surethe section chunks for headers and trailers for the lists are orderedas intended. This is done on all sections named .idata$*, before addingthe synthesized chunks to them.Differential Revision: https://reviews.llvm.org/D38513llvm-svn: 342777

            List of files:
            /llvm-project-15.0.7/lld/test/COFF/Inputs/gnu-implib-func.s</description>
        <pubDate>Fri, 21 Sep 2018 22:01:06 +0000</pubDate>
        <dc:creator>Martin Storsjo &lt;martin@martin.st&gt;</dc:creator>
    </item>
</channel>
</rss>
