mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-23 03:02:36 +01:00
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
This commit is contained in:
parent
09d40ae011
commit
95d4e72334
@ -134,7 +134,7 @@ void OptimizationRemarkEmitter::emit(DiagnosticInfoOptimizationBase &OptDiag) {
|
||||
computeHotness(OptDiag);
|
||||
|
||||
yaml::Output *Out = F->getContext().getDiagnosticsOutputFile();
|
||||
if (Out && OptDiag.isEnabled()) {
|
||||
if (Out) {
|
||||
auto *P = &const_cast<DiagnosticInfoOptimizationBase &>(OptDiag);
|
||||
*Out << P;
|
||||
}
|
||||
|
@ -1,6 +1,8 @@
|
||||
; RUN: opt < %s -S -inline -pass-remarks-missed=inline -pass-remarks-with-hotness \
|
||||
; RUN: -pass-remarks-output=%t 2>&1 | FileCheck %s
|
||||
; RUN: cat %t | FileCheck -check-prefix=YAML %s
|
||||
; RUN: opt < %s -S -inline -pass-remarks-with-hotness -pass-remarks-output=%t
|
||||
; RUN: cat %t | FileCheck -check-prefix=YAML %s
|
||||
|
||||
; Check the YAML file generated for inliner remarks for this program:
|
||||
;
|
||||
|
Loading…
Reference in New Issue
Block a user