Home | History | Annotate | only in /external/clang/test/Profile
Up to higher level directory
NameDateSize
c-attributes.c24-Aug-20161.2K
c-captured.c24-Aug-20162.3K
c-counter-overflows.c24-Aug-20161.9K
c-general.c24-Aug-201619.4K
c-generate.c24-Aug-2016488
c-linkage-available_externally.c24-Aug-2016941
c-linkage.c24-Aug-2016784
c-outdated-data.c24-Aug-2016815
c-unprofiled-blocks.c24-Aug-20161.9K
c-unprofiled.c24-Aug-2016995
c-unreachable-after-switch.c24-Aug-2016538
cxx-class.cpp24-Aug-20162.9K
cxx-implicit.cpp24-Aug-2016439
cxx-lambda.cpp24-Aug-20162.3K
cxx-linkage.cpp24-Aug-2016759
cxx-rangefor.cpp24-Aug-20161.6K
cxx-structors.cpp24-Aug-2016685
cxx-templates.cpp24-Aug-20161.9K
cxx-throws.cpp24-Aug-20163.5K
cxx-virtual-destructor-calls.cpp24-Aug-20161K
func-entry.c24-Aug-2016554
gcc-flag-compatibility.c24-Aug-20162.2K
Inputs/24-Aug-2016
max-function-count.c24-Aug-2016513
objc-general.m24-Aug-20162.5K
profile-does-not-exist.c24-Aug-2016207
README24-Aug-2016859

README

      1 These are tests for instrumentation based profiling.  This specifically means
      2 the -fprofile-instr-generate and -fprofile-instr-use driver flags.
      3 
      4 Tests 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 
      9 In order to test -fprofile-instr-use without actually running an instrumented
     10 program, .profdata files are checked into Inputs/.
     11 
     12 The 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
     15 tests that only check -fprofile-instr-use should include such a main function,
     16 so that profile data can be regenerated as the .profdata file format evolves.
     17