forked from OSchip/llvm-project
9121220804
Shared objects are fairly broken for InstrProf right now -- a follow-up commit in compiler-rt will fix the rest of this. The main problem here is that at link time, profile data symbols in the shared object might get used instead of symbols from the main executable, creating invalid profile data sections. <rdar://problem/16918688> llvm-svn: 208939 |
||
|---|---|---|
| .. | ||
| Inputs | ||
| README | ||
| c-attributes.c | ||
| c-captured.c | ||
| c-counter-overflows.c | ||
| c-general.c | ||
| c-linkage-available_externally.c | ||
| c-linkage.c | ||
| c-outdated-data.c | ||
| c-unprofiled-blocks.c | ||
| cxx-class.cpp | ||
| cxx-implicit.cpp | ||
| cxx-lambda.cpp | ||
| cxx-linkage.cpp | ||
| cxx-templates.cpp | ||
| cxx-throws.cpp | ||
| objc-general.m | ||
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.