Displaying 3 results from an estimated 3 matches for "getthreshold".
2017 Sep 16
3
RFC: Use closures to delay construction of optimization remarks
...<< NV("Caller", Caller) << "
because too costly to inline (cost="
Transforms/IPO/Inliner.cpp- << NV("Cost", IC.getCost())
Transforms/IPO/Inliner.cpp- << ", threshold=" <<
NV("Threshold", IC.getThreshold()) << ")");
Then inside ORE we return right away if the remarks for the given pass is
not enabled.
This is nice and concise however there is still some overhead involved in
this if remarks are not enabled:
1. Constructing the remark object
2. Computing and inserting the strings,...
2017 Sep 17
2
RFC: Use closures to delay construction of optimization remarks
...< NV("Caller", Caller) << " because too costly to inline (cost="
> Transforms/IPO/Inliner.cpp- << NV("Cost", IC.getCost())
> Transforms/IPO/Inliner.cpp- << ", threshold=" << NV("Threshold", IC.getThreshold()) << ")");
>
> Then inside ORE we return right away if the remarks for the given pass is not enabled.
>
> This is nice and concise however there is still some overhead involved in this if remarks are not enabled:
>
> 1. Constructing the remark object
> 2. Co...
2017 Sep 19
0
RFC: Use closures to delay construction of optimization remarks
..."Caller", Caller) << " because too costly to inline (cost="
>> Transforms/IPO/Inliner.cpp- << NV("Cost", IC.getCost())
>> Transforms/IPO/Inliner.cpp- << ", threshold=" << NV("Threshold", IC.getThreshold()) << ")");
>>
>> Then inside ORE we return right away if the remarks for the given pass is not enabled.
>>
>> This is nice and concise however there is still some overhead involved in this if remarks are not enabled:
>>
>> 1. Constructing the...