Don't filter diagnostics written as YAML to the output file
authorHal Finkel <hfinkel@anl.gov>
Tue, 4 Oct 2016 18:13:45 +0000 (18:13 +0000)
committerHal Finkel <hfinkel@anl.gov>
Tue, 4 Oct 2016 18:13:45 +0000 (18:13 +0000)
commitbdd6735a9e1ad7196c7d57dbda97ca91a97d7929
tree333828b0a40b1e05bc9ef81718ce03938dc286c1
parent56f453563440024d1beffe7fa20e81a358b31d0a
Don't filter diagnostics written as YAML to the output file

The purpose of the YAML diagnostic output file is to collect information on
optimizations performed, or not performed, for later processing by tools that
help users (and compiler developers) understand how code was optimized. As
such, the diagnostics that appear in the file should not be coupled to what a
user might want to see summarized for them as the compiler runs, and in fact,
because the user likely does not know what optimization diagnostics their tools
might want to use, the user cannot provide a useful filter regardless. As such,
we shouldn't filter the diagnostics going to the output file.

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

llvm-svn: 283236
llvm/lib/Analysis/OptimizationDiagnosticInfo.cpp
llvm/test/Transforms/Inline/optimization-remarks-yaml.ll