llvm-project

History

Leonard Chan ab2c0ed01e [clang][NewPM] Fix broken profile test This contains the part of D62225 which fixes Profile/gcc-flag-compatibility.c by adding the pass that allows default profile generation to work under the new PM. It seems that ./default.profraw was not being generated with new PM enabled. Differential Revision: https://reviews.llvm.org/D63155 llvm-svn: 363278		2019-06-13 17:25:36 +00:00
..
Inputs	…
README	…
c-avoid-direct-call.c	…
c-captured.c	…
c-counter-overflows.c	…
c-general.c	[PGO] Fix buildbot failure in 359215	2019-04-25 21:16:41 +00:00
c-generate.c	…
c-indirect-call.c	…
c-linkage-available_externally.c	…
c-linkage.c	…
c-outdated-data.c	…
c-ternary.c	…
c-unprofiled-blocks.c	…
c-unprofiled.c	…
c-unreachable-after-switch.c	…
cxx-abc-deleting-dtor.cpp	[MS] Don't emit coverage for deleting dtors	2019-02-26 20:42:52 +00:00
cxx-class.cpp	…
cxx-hash-v2.cpp	…
cxx-implicit.cpp	…
cxx-indirect-call.cpp	…
cxx-lambda.cpp	Fix clang tests broken by r353547 that depend on InstrProf	2019-02-10 20:17:07 +00:00
cxx-linkage.cpp	…
cxx-missing-bodies.cpp	…
cxx-rangefor.cpp	Fix clang tests broken by r353547 that depend on InstrProf	2019-02-10 20:17:07 +00:00
cxx-stmt-initializers.cpp	Fix clang tests broken by r353547 that depend on InstrProf	2019-02-10 20:17:07 +00:00
cxx-structors.cpp	…
cxx-templates.cpp	[InstrProf] Use separate comdat group for data and counters	2019-02-27 23:38:44 +00:00
cxx-throws.cpp	Fix clang tests broken by r353547 that depend on InstrProf	2019-02-10 20:17:07 +00:00
cxx-virtual-destructor-calls.cpp	Fix clang tests broken by r353547 that depend on InstrProf	2019-02-10 20:17:07 +00:00
def-assignop.cpp	…
def-ctors.cpp	…
def-dtors.cpp	…
func-entry.c	…
gcc-flag-compatibility.c	[clang][NewPM] Fix broken profile test	2019-06-13 17:25:36 +00:00
objc-general.m	…
profile-does-not-exist.c	…
profile-summary.c	…

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.