• Home
  • History
  • Annotate
  • only in /external/clang/test/Profile/
NameDateSize

..12-Mar-20154 KiB

c-attributes.c12-Mar-20151.2 KiB

c-captured.c12-Mar-20152.4 KiB

c-counter-overflows.c12-Mar-20151.9 KiB

c-general.c12-Mar-201519.6 KiB

c-linkage-available_externally.c12-Mar-2015930

c-linkage.c12-Mar-20153.4 KiB

c-outdated-data.c12-Mar-2015815

c-unprofiled-blocks.c12-Mar-20151.9 KiB

c-unprofiled.c12-Mar-2015995

cxx-class.cpp12-Mar-20153.1 KiB

cxx-implicit.cpp12-Mar-2015455

cxx-lambda.cpp12-Mar-20152.4 KiB

cxx-linkage.cpp12-Mar-20153.5 KiB

cxx-templates.cpp12-Mar-20151.9 KiB

cxx-throws.cpp12-Mar-20152.9 KiB

Inputs/12-Mar-20154 KiB

objc-general.m12-Mar-20152.5 KiB

README12-Mar-2015859

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