<?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 binary-formats.v6.linux64l</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>5fbd1a33 - [Coverage] Store compilation dir separately in coverage mapping</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/tools/llvm-cov/Inputs/binary-formats.v6.linux64l#5fbd1a33</link>
        <description>[Coverage] Store compilation dir separately in coverage mappingWe currently always store absolute filenames in coverage mapping.  Thisis problematic for several reasons. It poses a problem for distributedcompilation as source location might vary across machines.  We are alsoduplicating the path prefix potentially wasting space.This change modifies how we store filenames in coverage mapping. Ratherthan absolute paths, it stores the compilation directory and file pathsas given to the compiler, either relative or absolute. Later whenreading the coverage mapping information, we recombine relative pathswith the working directory. This approach is similar to handlingofDW_AT_comp_dir in DWARF.Finally, we also provide a new option, -fprofile-compilation-dir akinto -fdebug-compilation-dir which can be used to manually override thecompilation directory which is useful in distributed compilation cases.Differential Revision: https://reviews.llvm.org/D95753

            List of files:
            /llvm-project-15.0.7/llvm/test/tools/llvm-cov/Inputs/binary-formats.v6.linux64l</description>
        <pubDate>Wed, 10 Feb 2021 08:25:34 +0000</pubDate>
        <dc:creator>Petr Hosek &lt;phosek@google.com&gt;</dc:creator>
    </item>
<item>
        <title>97ec8fa5 - [Coverage] Store compilation dir separately in coverage mapping</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/tools/llvm-cov/Inputs/binary-formats.v6.linux64l#97ec8fa5</link>
        <description>[Coverage] Store compilation dir separately in coverage mappingWe currently always store absolute filenames in coverage mapping.  Thisis problematic for several reasons. It poses a problem for distributedcompilation as source location might vary across machines.  We are alsoduplicating the path prefix potentially wasting space.This change modifies how we store filenames in coverage mapping. Ratherthan absolute paths, it stores the compilation directory and file pathsas given to the compiler, either relative or absolute. Later whenreading the coverage mapping information, we recombine relative pathswith the working directory. This approach is similar to handlingofDW_AT_comp_dir in DWARF.Finally, we also provide a new option, -fprofile-compilation-dir akinto -fdebug-compilation-dir which can be used to manually override thecompilation directory which is useful in distributed compilation cases.Differential Revision: https://reviews.llvm.org/D95753

            List of files:
            /llvm-project-15.0.7/llvm/test/tools/llvm-cov/Inputs/binary-formats.v6.linux64l</description>
        <pubDate>Wed, 10 Feb 2021 08:25:34 +0000</pubDate>
        <dc:creator>Petr Hosek &lt;phosek@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
