hanchenye-llvm-project

History

Justin Bogner 534f14abe7 test: Use llvm-profdata merge in Profile tests In preparation for using a binary format for instrumentation based profiling, explicitly treat the test inputs as text and transform them before running. This will allow us to leave the checked in files in human readable format once the instrumentation format is binary. No functional change. llvm-svn: 206509		2014-04-17 22:49:06 +00:00
..
Inputs	test: Use llvm-profdata merge in Profile tests	2014-04-17 22:49:06 +00:00
README	PGO: Clarify the testing README	2014-03-11 18:18:12 +00:00
c-attributes.c	test: Use llvm-profdata merge in Profile tests	2014-04-17 22:49:06 +00:00
c-captured.c	test: Use llvm-profdata merge in Profile tests	2014-04-17 22:49:06 +00:00
c-counter-overflows.c	test: Use llvm-profdata merge in Profile tests	2014-04-17 22:49:06 +00:00
c-general.c	test: Use llvm-profdata merge in Profile tests	2014-04-17 22:49:06 +00:00
c-linkage-available_externally.c	InstrProf: Calculate a better function hash	2014-04-16 16:03:27 +00:00
c-linkage.c	InstrProf: Calculate a better function hash	2014-04-16 16:03:27 +00:00
c-outdated-data.c	test: Use llvm-profdata merge in Profile tests	2014-04-17 22:49:06 +00:00
c-unprofiled-blocks.c	test: Use llvm-profdata merge in Profile tests	2014-04-17 22:49:06 +00:00
cxx-class.cpp	test: Use llvm-profdata merge in Profile tests	2014-04-17 22:49:06 +00:00
cxx-lambda.cpp	test: Use llvm-profdata merge in Profile tests	2014-04-17 22:49:06 +00:00
cxx-linkage.cpp	InstrProf: Calculate a better function hash	2014-04-16 16:03:27 +00:00
cxx-templates.cpp	test: Use llvm-profdata merge in Profile tests	2014-04-17 22:49:06 +00:00
cxx-throws.cpp	test: Use llvm-profdata merge in Profile tests	2014-04-17 22:49:06 +00:00
objc-general.m	test: Use llvm-profdata merge in Profile tests	2014-04-17 22:49:06 +00: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.