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

..03-May-2022-

Inputs/H03-May-2022-815709

READMEH A D20-Jan-2022859 1712

branch-logical-mixed.cppH A D20-Jan-20222.8 KiB6751

branch-profdup.cppH A D20-Jan-20221.9 KiB7740

c-avoid-direct-call.cH A D20-Jan-2022365 125

c-captured.cH A D20-Jan-20222.3 KiB6018

c-collision.cH A D20-Jan-2022799 2315

c-counter-overflows.cH A D20-Jan-20221.9 KiB5019

c-general.cH A D20-Jan-202220.4 KiB576184

c-generate.cH A D20-Jan-2022708 153

c-indirect-call.cH A D20-Jan-20221.2 KiB235

c-linkage-available_externally.cH A D20-Jan-2022705 124

c-linkage.cH A D20-Jan-2022889 2711

c-outdated-data.cH A D20-Jan-20221.2 KiB2910

c-ternary.cH A D20-Jan-2022751 163

c-unprofiled-blocks.cH A D20-Jan-20221.9 KiB7031

c-unprofiled.cH A D20-Jan-20221,005 2712

c-unreachable-after-switch.cH A D20-Jan-2022538 166

coverage-prefix-map.cH A D20-Jan-20222 KiB220

cxx-abc-deleting-dtor.cppH A D20-Jan-20223.3 KiB849

cxx-class.cppH A D20-Jan-20224.2 KiB11333

cxx-hash-v2.cppH A D20-Jan-20222.7 KiB178137

cxx-implicit.cppH A D20-Jan-20221.5 KiB5227

cxx-indirect-call.cppH A D20-Jan-2022727 227

cxx-lambda.cppH A D20-Jan-20222.5 KiB5915

cxx-linkage.cppH A D20-Jan-2022863 2611

cxx-missing-bodies.cppH A D20-Jan-2022643 2210

cxx-rangefor.cppH A D20-Jan-20221.7 KiB4516

cxx-stmt-initializers.cppH A D20-Jan-20221.3 KiB306

cxx-structors.cppH A D20-Jan-20221.2 KiB5626

cxx-templates.cppH A D20-Jan-20221.9 KiB438

cxx-throws.cppH A D20-Jan-20223.6 KiB9428

cxx-virtual-destructor-calls.cppH A D20-Jan-2022803 2911

def-assignop.cppH A D20-Jan-20221.3 KiB3514

def-ctors.cppH A D20-Jan-20221.5 KiB4116

def-dtors.cppH A D20-Jan-20221.2 KiB3515

func-entry.cH A D20-Jan-2022574 207

gcc-flag-compatibility.cH A D20-Jan-20224.3 KiB677

objc-general.mH A D20-Jan-20222.7 KiB9274

profile-does-not-exist.cH A D20-Jan-2022217 50

profile-summary.cH A D20-Jan-2022571 2616

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