Name
Date
Size
#Lines
LOC

..--

Inputs/H--411352

READMEH A D15-Oct-2015859 1712

c-attributes.cH A D15-Oct-20151.2 KiB4930

c-captured.cH A D15-Oct-20152.3 KiB6018

c-counter-overflows.cH A D15-Oct-20151.9 KiB5019

c-general.cH A D15-Oct-201518.7 KiB548184

c-linkage-available_externally.cH A D15-Oct-2015931 144

c-linkage.cH A D15-Oct-20153.5 KiB3911

c-outdated-data.cH A D15-Oct-2015815 2915

c-unprofiled-blocks.cH A D15-Oct-20151.9 KiB7031

c-unprofiled.cH A D15-Oct-2015995 2712

c-unreachable-after-switch.cH A D15-Oct-2015553 166

cxx-class.cppH A D15-Oct-20153 KiB7923

cxx-implicit.cppH A D15-Oct-2015455 187

cxx-lambda.cppH A D15-Oct-20152.3 KiB5915

cxx-linkage.cppH A D15-Oct-20153.5 KiB3811

cxx-templates.cppH A D15-Oct-20151.9 KiB438

cxx-throws.cppH A D15-Oct-20152.8 KiB7420

objc-general.mH A D15-Oct-20152.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