llvm-project/clang/test/Frontend/Inputs
Vedant Kumar 6186971a4a [PGO] Detect more structural changes with the stable hash
Lifting from Bob Wilson's notes: The hash value that we compute and
store in PGO profile data to detect out-of-date profiles does not
include enough information. This means that many significant changes to
the source will not cause compiler warnings about the profile being out
of date, and worse, we may continue to use the outdated profile data to
make bad optimization decisions.  There is some tension here because
some source changes won't affect PGO and we don't want to invalidate the
profile unnecessarily.

This patch adds a new hashing scheme which is more sensitive to loop
nesting, conditions, and out-of-order control flow. Here are examples
which show snippets which get the same hash under the current scheme,
and different hashes under the new scheme:

Loop Nesting Example
--------------------

  // Snippet 1
  while (foo()) {
    while (bar()) {}
  }

  // Snippet 2
  while (foo()) {}
  while (bar()) {}

Condition Example
-----------------

  // Snippet 1
  if (foo())
    bar();
  baz();

  // Snippet 2
  if (foo())
    bar();
  else
    baz();

Out-of-order Control Flow Example
---------------------------------

  // Snippet 1
  while (foo()) {
    if (bar()) {}
    baz();
  }

  // Snippet 2
  while (foo()) {
    if (bar())
      continue;
    baz();
  }

In each of these cases, it's useful to differentiate between the
snippets because swapping their profiles gives bad optimization hints.

The new hashing scheme considers some logical operators in an effort to
detect more changes in conditions. This isn't a perfect scheme. E.g, it
does not produce the same hash for these equivalent snippets:

  // Snippet 1
  bool c = !a || b;
  if (d && e) {}

  // Snippet 2
  bool f = d && e;
  bool c = !a || b;
  if (f) {}

This would require an expensive data flow analysis. Short of that, the
new hashing scheme looks reasonably complete, based on a scan over the
statements we place counters on.

Profiles which use the old version of the PGO hash remain valid and can
be used without issue (there are tests in tree which check this).

rdar://17068282

Differential Revision: https://reviews.llvm.org/D39446

llvm-svn: 318229
2017-11-14 23:56:53 +00:00
..
SystemHeaderPrefix Add test coverage for recent behavior change in GNU line marker pre-processing 2017-05-23 16:09:13 +00:00
TestFramework.framework/Headers
absolute-paths.h
empty.h PR26771: don't forget the " 2" (returning from #included file) linemarker after including an empty file with -frewrite-includes. 2017-04-29 00:54:03 +00:00
line-directive.h Add test coverage for recent behavior change in GNU line marker pre-processing 2017-05-23 16:09:13 +00:00
optimization-remark-with-hotness-sample.proftext Un-revert "[Driver] Add -fdiagnostics-hotness-threshold" 2017-07-01 05:45:26 +00:00
optimization-remark-with-hotness.proftext [PGO] Detect more structural changes with the stable hash 2017-11-14 23:56:53 +00:00
profile-sample-use-loc-tracking.prof
rewrite-includes-bom.h
rewrite-includes-messages.h
rewrite-includes1.h
rewrite-includes2.h
rewrite-includes3.h
rewrite-includes4.h
rewrite-includes5.h
rewrite-includes6.h
rewrite-includes7.h
rewrite-includes8.h
test.h
test2.h
test3.h