nuudlman / llvm

guest › [sign in] [explore]

{/} code [~] changes [>] discussions [*] jobs

mode name

drwxr-xr-x Inputs/

-rw-r--r-- README

-rw-r--r-- branch-logical-mixed.cpp

-rw-r--r-- branch-profdup.cpp

-rw-r--r-- c-avoid-direct-call.c

-rw-r--r-- c-captured.c

-rw-r--r-- c-collision.c

-rw-r--r-- c-counter-overflows.c

-rw-r--r-- c-general.c

-rw-r--r-- c-generate.c

-rw-r--r-- c-indirect-call.c

-rw-r--r-- c-linkage-available_externally.c

-rw-r--r-- c-linkage.c

-rw-r--r-- c-outdated-data.c

-rw-r--r-- c-ternary.c

-rw-r--r-- c-unprofiled-blocks.c

-rw-r--r-- c-unprofiled.c

-rw-r--r-- c-unreachable-after-switch.c

-rw-r--r-- coverage-prefix-map.c

-rw-r--r-- cxx-abc-deleting-dtor.cpp

-rw-r--r-- cxx-class.cpp

-rw-r--r-- cxx-hash-v2.cpp

-rw-r--r-- cxx-implicit.cpp

-rw-r--r-- cxx-indirect-call.cpp

-rw-r--r-- cxx-lambda.cpp

-rw-r--r-- cxx-linkage.cpp

-rw-r--r-- cxx-missing-bodies.cpp

-rw-r--r-- cxx-rangefor.cpp

-rw-r--r-- cxx-stmt-initializers.cpp

-rw-r--r-- cxx-structors.cpp

-rw-r--r-- cxx-templates.cpp

-rw-r--r-- cxx-throws.cpp

-rw-r--r-- cxx-virtual-destructor-calls.cpp

-rw-r--r-- def-assignop.cpp

-rw-r--r-- def-ctors.cpp

-rw-r--r-- def-dtors.cpp

-rw-r--r-- func-entry.c

-rw-r--r-- gcc-flag-compatibility-aix.c

-rw-r--r-- gcc-flag-compatibility.c

-rw-r--r-- misexpect-branch-cold.c

-rw-r--r-- misexpect-branch-nonconst-expected-val.c

-rw-r--r-- misexpect-branch-unpredictable.c

-rw-r--r-- misexpect-branch.c

-rw-r--r-- misexpect-switch-default.c

-rw-r--r-- misexpect-switch-nonconst.c

-rw-r--r-- misexpect-switch-only-default-case.c

-rw-r--r-- misexpect-switch.c

-rw-r--r-- objc-general.m

-rw-r--r-- profile-does-not-exist.c

-rw-r--r-- profile-summary.c

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.