• Home
Name Date Size #Lines LOC

..--

Inputs/03-May-2024-411352

READMED03-May-2024859 1712

c-attributes.cD03-May-20241.2 KiB4930

c-captured.cD03-May-20242.4 KiB6018

c-counter-overflows.cD03-May-20241.9 KiB5019

c-general.cD03-May-202419.6 KiB545184

c-linkage-available_externally.cD03-May-2024930 134

c-linkage.cD03-May-20243.4 KiB3811

c-outdated-data.cD03-May-2024815 2915

c-unprofiled-blocks.cD03-May-20241.9 KiB7031

c-unprofiled.cD03-May-2024995 2712

cxx-class.cppD03-May-20243.1 KiB7923

cxx-implicit.cppD03-May-2024455 187

cxx-lambda.cppD03-May-20242.4 KiB5915

cxx-linkage.cppD03-May-20243.5 KiB3711

cxx-templates.cppD03-May-20241.9 KiB438

cxx-throws.cppD03-May-20242.9 KiB7420

objc-general.mD03-May-20242.5 KiB7661

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