Home | History | Annotate | only in /external/clang/test/Profile
Up to higher level directory
NameDateSize
c-attributes.c23-Apr-20151.2K
c-captured.c23-Apr-20152.4K
c-counter-overflows.c23-Apr-20151.9K
c-general.c23-Apr-201519.6K
c-linkage-available_externally.c23-Apr-2015930
c-linkage.c23-Apr-20153.4K
c-outdated-data.c23-Apr-2015815
c-unprofiled-blocks.c23-Apr-20151.9K
c-unprofiled.c23-Apr-2015995
cxx-class.cpp23-Apr-20153.1K
cxx-implicit.cpp23-Apr-2015455
cxx-lambda.cpp23-Apr-20152.4K
cxx-linkage.cpp23-Apr-20153.5K
cxx-templates.cpp23-Apr-20151.9K
cxx-throws.cpp23-Apr-20152.9K
Inputs/23-Apr-2015
objc-general.m23-Apr-20152.5K
README23-Apr-2015859

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