This is an archive of the discontinued LLVM Phabricator instance.

PGOInstrumentation: Move profile matching warnings to remarks
AbandonedPublic

Authored by dblaikie on Jul 13 2017, 1:56 PM.

Details

Reviewers
davidxl
chandlerc
Summary

These messages are expected if the source code has diverged sufficiently
from the code the profile was gathered from. In small enough amounts
they're benign/not actionable, so a warning seems inappropriate/noisy (&
probablematic in -Werror builds) for these kinds of messages.

I also updated some tests around other profile instrumentation related
diagnostics to ensure they are errors (things like failing to load the
profile, finding it's the wrong kind of profile - these are actionable
by the user) & removed one that wasn't reachable/testable, but was
testing an API invariant - replaced that with an assertion.

Event Timeline

dblaikie created this revision.Jul 13 2017, 1:56 PM
davidxl edited edge metadata.Jul 13 2017, 2:03 PM

Blindly downgrade the warning into remarks can be bad -- profile mismatch problems can go undetected. People may spend more time diagnosing performance regressions due to missed warnings. Worse, we may regress in compiler without noticing.

dblaikie abandoned this revision.Oct 24 2019, 7:30 PM

I /think/ this is probably still the right direction, but haven't got the context/prioritization/etc to make progress here, so abandoning (finding retired old branches as I migrate to the git repo from git-svn).