Marcelo Lopez Ruiz
6ee4074a4b
first commit
|
9 years ago | |
|---|---|---|
| .. | ||
| Inputs | 9 years ago | |
| README | 9 years ago | |
| c-attributes.c | 9 years ago | |
| c-captured.c | 9 years ago | |
| c-counter-overflows.c | 9 years ago | |
| c-general.c | 9 years ago | |
| c-generate.c | 9 years ago | |
| c-linkage-available_externally.c | 9 years ago | |
| c-linkage.c | 9 years ago | |
| c-outdated-data.c | 9 years ago | |
| c-unprofiled-blocks.c | 9 years ago | |
| c-unprofiled.c | 9 years ago | |
| c-unreachable-after-switch.c | 9 years ago | |
| cxx-class.cpp | 9 years ago | |
| cxx-implicit.cpp | 9 years ago | |
| cxx-lambda.cpp | 9 years ago | |
| cxx-linkage.cpp | 9 years ago | |
| cxx-rangefor.cpp | 9 years ago | |
| cxx-templates.cpp | 9 years ago | |
| cxx-throws.cpp | 9 years ago | |
| cxx-virtual-destructor-calls.cpp | 9 years ago | |
| func-entry.c | 9 years ago | |
| gcc-flag-compatibility.c | 9 years ago | |
| profile-does-not-exist.c | 9 years ago | |
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.
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.