fuquan/android_mt6572_jiabo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
android_mt6572_jiabo/external/clang/test/Profile
History
Exact
FuQuan 3ff2876a30 first commit
2025-09-05 16:56:03 +08:00
..
Inputs first commit 2025-09-05 16:56:03 +08:00
c-attributes.c first commit 2025-09-05 16:56:03 +08:00
c-captured.c first commit 2025-09-05 16:56:03 +08:00
c-counter-overflows.c first commit 2025-09-05 16:56:03 +08:00
c-general.c first commit 2025-09-05 16:56:03 +08:00
c-generate.c first commit 2025-09-05 16:56:03 +08:00
c-linkage-available_externally.c first commit 2025-09-05 16:56:03 +08:00
c-linkage.c first commit 2025-09-05 16:56:03 +08:00
c-outdated-data.c first commit 2025-09-05 16:56:03 +08:00
c-unprofiled-blocks.c first commit 2025-09-05 16:56:03 +08:00
c-unprofiled.c first commit 2025-09-05 16:56:03 +08:00
c-unreachable-after-switch.c first commit 2025-09-05 16:56:03 +08:00
cxx-class.cpp first commit 2025-09-05 16:56:03 +08:00
cxx-implicit.cpp first commit 2025-09-05 16:56:03 +08:00
cxx-lambda.cpp first commit 2025-09-05 16:56:03 +08:00
cxx-linkage.cpp first commit 2025-09-05 16:56:03 +08:00
cxx-rangefor.cpp first commit 2025-09-05 16:56:03 +08:00
cxx-structors.cpp first commit 2025-09-05 16:56:03 +08:00
cxx-templates.cpp first commit 2025-09-05 16:56:03 +08:00
cxx-throws.cpp first commit 2025-09-05 16:56:03 +08:00
cxx-virtual-destructor-calls.cpp first commit 2025-09-05 16:56:03 +08:00
func-entry.c first commit 2025-09-05 16:56:03 +08:00
gcc-flag-compatibility.c first commit 2025-09-05 16:56:03 +08:00
max-function-count.c first commit 2025-09-05 16:56:03 +08:00
objc-general.m first commit 2025-09-05 16:56:03 +08:00
profile-does-not-exist.c first commit 2025-09-05 16:56:03 +08:00
README first commit 2025-09-05 16:56:03 +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.