tree ce13a0cad83e55385931821d82dde0a708f0ae7c
parent c0e5f628c4ef83e813ecad07d7199d058baeef60
author Petr Hosek <phosek@google.com> 1612945534 -0800
committer Copybara-Service <copybara-worker@google.com> 1613735036 -0800

[Coverage] Store compilation dir separately in coverage mapping

We currently always store absolute filenames in coverage mapping.  This
is problematic for several reasons. It poses a problem for distributed
compilation as source location might vary across machines.  We are also
duplicating the path prefix potentially wasting space.

This change modifies how we store filenames in coverage mapping. Rather
than absolute paths, it stores the compilation directory and file paths
as given to the compiler, either relative or absolute. Later when
reading the coverage mapping information, we recombine relative paths
with the working directory. This approach is similar to handling
ofDW_AT_comp_dir in DWARF.

Finally, we also provide a new option, -fprofile-compilation-dir akin
to -fdebug-compilation-dir which can be used to manually override the
compilation directory which is useful in distributed compilation cases.

Differential Revision: https://reviews.llvm.org/D95753

GitOrigin-RevId: 5fbd1a333aa1a0b70903d036b98ea56c51ae5224