• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

Inputs/22-Nov-2023-411352

READMED22-Nov-2023859 1712

c-attributes.cD22-Nov-20231.2 KiB4930

c-captured.cD22-Nov-20232.3 KiB6018

c-counter-overflows.cD22-Nov-20231.9 KiB5019

c-general.cD22-Nov-202318.7 KiB548184

c-linkage-available_externally.cD22-Nov-2023952 144

c-linkage.cD22-Nov-2023834 2311

c-outdated-data.cD22-Nov-2023815 2915

c-unprofiled-blocks.cD22-Nov-20231.9 KiB7031

c-unprofiled.cD22-Nov-2023995 2712

c-unreachable-after-switch.cD22-Nov-2023554 166

cxx-class.cppD22-Nov-20233 KiB7923

cxx-implicit.cppD22-Nov-2023455 187

cxx-lambda.cppD22-Nov-20232.3 KiB5915

cxx-linkage.cppD22-Nov-2023807 2211

cxx-templates.cppD22-Nov-20231.9 KiB438

cxx-throws.cppD22-Nov-20232.9 KiB7420

objc-general.mD22-Nov-20232.5 KiB7661

profile-does-not-exist.cD22-Nov-2023179 50

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