android13/external/clang/test/Profile
liiir1985 7f62dcda9f initial 2024-06-22 20:45:49 +08:00
..
Inputs initial 2024-06-22 20:45:49 +08:00
README initial 2024-06-22 20:45:49 +08:00
c-avoid-direct-call.c initial 2024-06-22 20:45:49 +08:00
c-captured.c initial 2024-06-22 20:45:49 +08:00
c-counter-overflows.c initial 2024-06-22 20:45:49 +08:00
c-general.c initial 2024-06-22 20:45:49 +08:00
c-generate.c initial 2024-06-22 20:45:49 +08:00
c-indirect-call.c initial 2024-06-22 20:45:49 +08:00
c-linkage-available_externally.c initial 2024-06-22 20:45:49 +08:00
c-linkage.c initial 2024-06-22 20:45:49 +08:00
c-outdated-data.c initial 2024-06-22 20:45:49 +08:00
c-unprofiled-blocks.c initial 2024-06-22 20:45:49 +08:00
c-unprofiled.c initial 2024-06-22 20:45:49 +08:00
c-unreachable-after-switch.c initial 2024-06-22 20:45:49 +08:00
cxx-class.cpp initial 2024-06-22 20:45:49 +08:00
cxx-implicit.cpp initial 2024-06-22 20:45:49 +08:00
cxx-indirect-call.cpp initial 2024-06-22 20:45:49 +08:00
cxx-lambda.cpp initial 2024-06-22 20:45:49 +08:00
cxx-linkage.cpp initial 2024-06-22 20:45:49 +08:00
cxx-rangefor.cpp initial 2024-06-22 20:45:49 +08:00
cxx-structors.cpp initial 2024-06-22 20:45:49 +08:00
cxx-templates.cpp initial 2024-06-22 20:45:49 +08:00
cxx-throws.cpp initial 2024-06-22 20:45:49 +08:00
cxx-virtual-destructor-calls.cpp initial 2024-06-22 20:45:49 +08:00
def-assignop.cpp initial 2024-06-22 20:45:49 +08:00
def-ctors.cpp initial 2024-06-22 20:45:49 +08:00
def-dtors.cpp initial 2024-06-22 20:45:49 +08:00
func-entry.c initial 2024-06-22 20:45:49 +08:00
gcc-flag-compatibility.c initial 2024-06-22 20:45:49 +08:00
objc-general.m initial 2024-06-22 20:45:49 +08:00
profile-does-not-exist.c initial 2024-06-22 20:45:49 +08:00
profile-summary.c initial 2024-06-22 20:45:49 +08:00

README

These are tests for instrumentation based profiling.  This specifically means
the -fprofile-instr-generate and -fprofile-instr-use driver flags.

Tests in this directory should usually test both:

  - the generation of instrumentation (-fprofile-instr-generate), and
  - the use of profile data from instrumented runs (-fprofile-instr-use).

In order to test -fprofile-instr-use without actually running an instrumented
program, .profdata files are checked into Inputs/.

The input source files must include a main function such that building with
-fprofile-instr-generate and running the resulting program generates the same
.profdata file that is consumed by the tests for -fprofile-instr-use.  Even
tests that only check -fprofile-instr-use should include such a main function,
so that profile data can be regenerated as the .profdata file format evolves.