Name | Date | Size | |
---|---|---|---|
.. | 29-Aug-2017 | 4 KiB | |
c-avoid-direct-call.c | 29-Aug-2017 | 365 | |
c-captured.c | 29-Aug-2017 | 2.3 KiB | |
c-counter-overflows.c | 29-Aug-2017 | 1.9 KiB | |
c-general.c | 29-Aug-2017 | 19.5 KiB | |
c-generate.c | 29-Aug-2017 | 947 | |
c-indirect-call.c | 29-Aug-2017 | 681 | |
c-linkage-available_externally.c | 29-Aug-2017 | 684 | |
c-linkage.c | 29-Aug-2017 | 889 | |
c-outdated-data.c | 29-Aug-2017 | 825 | |
c-unprofiled-blocks.c | 29-Aug-2017 | 1.9 KiB | |
c-unprofiled.c | 29-Aug-2017 | 1,005 | |
c-unreachable-after-switch.c | 29-Aug-2017 | 540 | |
cxx-class.cpp | 29-Aug-2017 | 2.9 KiB | |
cxx-implicit.cpp | 29-Aug-2017 | 1.5 KiB | |
cxx-indirect-call.cpp | 29-Aug-2017 | 723 | |
cxx-lambda.cpp | 29-Aug-2017 | 2.3 KiB | |
cxx-linkage.cpp | 29-Aug-2017 | 863 | |
cxx-rangefor.cpp | 29-Aug-2017 | 1.6 KiB | |
cxx-structors.cpp | 29-Aug-2017 | 687 | |
cxx-templates.cpp | 29-Aug-2017 | 1.9 KiB | |
cxx-throws.cpp | 29-Aug-2017 | 3.5 KiB | |
cxx-virtual-destructor-calls.cpp | 29-Aug-2017 | 1.1 KiB | |
def-assignop.cpp | 29-Aug-2017 | 1.2 KiB | |
def-ctors.cpp | 29-Aug-2017 | 1.3 KiB | |
def-dtors.cpp | 29-Aug-2017 | 1 KiB | |
func-entry.c | 29-Aug-2017 | 574 | |
gcc-flag-compatibility.c | 29-Aug-2017 | 2.2 KiB | |
Inputs/ | 29-Aug-2017 | 4 KiB | |
objc-general.m | 29-Aug-2017 | 2.5 KiB | |
profile-does-not-exist.c | 29-Aug-2017 | 217 | |
profile-summary.c | 29-Aug-2017 | 571 | |
README | 29-Aug-2017 | 859 |
README
1These are tests for instrumentation based profiling. This specifically means 2the -fprofile-instr-generate and -fprofile-instr-use driver flags. 3 4Tests in this directory should usually test both: 5 6 - the generation of instrumentation (-fprofile-instr-generate), and 7 - the use of profile data from instrumented runs (-fprofile-instr-use). 8 9In order to test -fprofile-instr-use without actually running an instrumented 10program, .profdata files are checked into Inputs/. 11 12The input source files must include a main function such that building with 13-fprofile-instr-generate and running the resulting program generates the same 14.profdata file that is consumed by the tests for -fprofile-instr-use. Even 15tests that only check -fprofile-instr-use should include such a main function, 16so that profile data can be regenerated as the .profdata file format evolves. 17