Displaying 3 results from an estimated 3 matches for "optimizationremarkmiss".
Did you mean:
optimizationremarkmissed
2017 Sep 16
3
RFC: Use closures to delay construction of optimization remarks
...t-circuits all the stream operations)
On Sep 15, 2017 2:21 PM, "Adam Nemet via llvm-dev" <llvm-dev at lists.llvm.org>
wrote:
For better readability we typically create remarks and call
OptimizationRemarkEmitter::emit unconditionally. E.g.:
Transforms/IPO/Inliner.cpp: ORE.emit(OptimizationRemarkMissed(DEBUG_TYPE,
"TooCostly", Call)
Transforms/IPO/Inliner.cpp- << NV("Callee", Callee) << " not
inlined into "
Transforms/IPO/Inliner.cpp- << NV("Caller", Caller) << "
because too costly to inline (cost="...
2017 Sep 17
2
RFC: Use closures to delay construction of optimization remarks
...:21 PM, "Adam Nemet via llvm-dev" <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> For better readability we typically create remarks and call OptimizationRemarkEmitter::emit unconditionally. E.g.:
>
> Transforms/IPO/Inliner.cpp: ORE.emit(OptimizationRemarkMissed(DEBUG_TYPE, "TooCostly", Call)
> Transforms/IPO/Inliner.cpp- << NV("Callee", Callee) << " not inlined into "
> Transforms/IPO/Inliner.cpp- << NV("Caller", Caller) << " because too costly to inline (...
2017 Sep 19
0
RFC: Use closures to delay construction of optimization remarks
...t;Adam Nemet via llvm-dev" <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>> For better readability we typically create remarks and call OptimizationRemarkEmitter::emit unconditionally. E.g.:
>>
>> Transforms/IPO/Inliner.cpp: ORE.emit(OptimizationRemarkMissed(DEBUG_TYPE, "TooCostly", Call)
>> Transforms/IPO/Inliner.cpp- << NV("Callee", Callee) << " not inlined into "
>> Transforms/IPO/Inliner.cpp- << NV("Caller", Caller) << " because too costly to...