Home | History | Annotate | only in /external/clang/test/Profile
Up to higher level directory
NameDateSize
c-attributes.c08-Oct-20151.2K
c-captured.c08-Oct-20152.3K
c-counter-overflows.c08-Oct-20151.9K
c-general.c08-Oct-201518.7K
c-linkage-available_externally.c08-Oct-2015952
c-linkage.c08-Oct-2015834
c-outdated-data.c08-Oct-2015815
c-unprofiled-blocks.c08-Oct-20151.9K
c-unprofiled.c08-Oct-2015995
c-unreachable-after-switch.c08-Oct-2015554
cxx-class.cpp08-Oct-20153K
cxx-implicit.cpp08-Oct-2015455
cxx-lambda.cpp08-Oct-20152.3K
cxx-linkage.cpp08-Oct-2015807
cxx-templates.cpp08-Oct-20151.9K
cxx-throws.cpp08-Oct-20152.9K
Inputs/08-Oct-2015
objc-general.m08-Oct-20152.5K
profile-does-not-exist.c08-Oct-2015179
README08-Oct-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