forked from OSchip/llvm-project
5fbd1a333a
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 |
||
|---|---|---|
| .. | ||
| Inputs | ||
| README | ||
| branch-logical-mixed.cpp | ||
| branch-profdup.cpp | ||
| c-avoid-direct-call.c | ||
| c-captured.c | ||
| c-collision.c | ||
| c-counter-overflows.c | ||
| c-general.c | ||
| c-generate.c | ||
| c-indirect-call.c | ||
| c-linkage-available_externally.c | ||
| c-linkage.c | ||
| c-outdated-data.c | ||
| c-ternary.c | ||
| c-unprofiled-blocks.c | ||
| c-unprofiled.c | ||
| c-unreachable-after-switch.c | ||
| cxx-abc-deleting-dtor.cpp | ||
| cxx-class.cpp | ||
| cxx-hash-v2.cpp | ||
| cxx-implicit.cpp | ||
| cxx-indirect-call.cpp | ||
| cxx-lambda.cpp | ||
| cxx-linkage.cpp | ||
| cxx-missing-bodies.cpp | ||
| cxx-rangefor.cpp | ||
| cxx-stmt-initializers.cpp | ||
| cxx-structors.cpp | ||
| cxx-templates.cpp | ||
| cxx-throws.cpp | ||
| cxx-virtual-destructor-calls.cpp | ||
| def-assignop.cpp | ||
| def-ctors.cpp | ||
| def-dtors.cpp | ||
| func-entry.c | ||
| gcc-flag-compatibility.c | ||
| objc-general.m | ||
| profile-does-not-exist.c | ||
| profile-prefix-map.c | ||
| profile-summary.c | ||
README
These are tests for instrumentation based profiling. This specifically means the -fprofile-instr-generate and -fprofile-instr-use driver flags. Tests in this directory should usually test both: - the generation of instrumentation (-fprofile-instr-generate), and - the use of profile data from instrumented runs (-fprofile-instr-use). In order to test -fprofile-instr-use without actually running an instrumented program, .profdata files are checked into Inputs/. The input source files must include a main function such that building with -fprofile-instr-generate and running the resulting program generates the same .profdata file that is consumed by the tests for -fprofile-instr-use. Even tests that only check -fprofile-instr-use should include such a main function, so that profile data can be regenerated as the .profdata file format evolves.