summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/bench.py
diff options
context:
space:
mode:
authorHal Finkel <hfinkel@anl.gov>2016-10-04 18:13:45 +0000
committerHal Finkel <hfinkel@anl.gov>2016-10-04 18:13:45 +0000
commitbdd6735a9e1ad7196c7d57dbda97ca91a97d7929 (patch)
tree333828b0a40b1e05bc9ef81718ce03938dc286c1 /lldb/packages/Python/lldbsuite/test/bench.py
parent56f453563440024d1beffe7fa20e81a358b31d0a (diff)
downloadbcm5719-llvm-bdd6735a9e1ad7196c7d57dbda97ca91a97d7929.tar.gz
bcm5719-llvm-bdd6735a9e1ad7196c7d57dbda97ca91a97d7929.zip
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
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/bench.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud