forked from OSchip/llvm-project
9c6f1538cc
This patch changes cc1 option for PGO profile use from
-fprofile-instr-use=<path> to -fprofile-instrument-use-path=<path>.
-fprofile-instr-use=<path> is now a driver only option.
In addition to decouple the cc1 option from the driver level option, this patch
also enables IR level profile use. cc1 option handling now reads the profile
header and sets CodeGenOpt ProfileUse (valid values are {None, Clang, LLVM}
-- this is a common enum for -fprofile-instrument={}, for the profile
instrumentation), and invoke the pipeline to enable the respective PGO use pass.
Reviewers: silvas, davidxl
Differential Revision: http://reviews.llvm.org/D17737
llvm-svn: 262515
|
||
|---|---|---|
| .. | ||
| Inputs | ||
| README | ||
| c-captured.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-unprofiled-blocks.c | ||
| c-unprofiled.c | ||
| c-unreachable-after-switch.c | ||
| cxx-class.cpp | ||
| cxx-implicit.cpp | ||
| cxx-lambda.cpp | ||
| cxx-linkage.cpp | ||
| cxx-rangefor.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 | ||
| max-function-count.c | ||
| objc-general.m | ||
| profile-does-not-exist.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.