Displaying 3 results from an estimated 3 matches for "d37921".
Did you mean:
37921
2017 Sep 16
3
RFC: Use closures to delay construction of optimization remarks
...too costly to inline
(cost="
<< NV("Cost", IC.getCost())
<< ", threshold=" << NV("Threshold", IC.getThreshold()) << ")"
*;*
* }*);
I have a proof-of-concept implementation at https://reviews.llvm.org/D37921.
The main change is that since in the lambda the remark is now returned by
value, we need to preserve its type in the insertion operator. This
requires making the insertion operator generic. I am also curious if
people see C++ portability problems with the code.
Feedback welcome.
Adam
[1] htt...
2017 Sep 17
2
RFC: Use closures to delay construction of optimization remarks
...t="
> << NV("Cost", IC.getCost())
> << ", threshold=" << NV("Threshold", IC.getThreshold()) << ")";
> });
>
>
> I have a proof-of-concept implementation at https://reviews.llvm.org/D37921 <https://reviews.llvm.org/D37921>.
>
> The main change is that since in the lambda the remark is now returned by value, we need to preserve its type in the insertion operator. This requires making the insertion operator generic. I am also curious if people see C++ portability proble...
2017 Sep 19
0
RFC: Use closures to delay construction of optimization remarks
...<< NV("Cost", IC.getCost())
>> << ", threshold=" << NV("Threshold", IC.getThreshold()) << ")";
>> });
>>
>>
>> I have a proof-of-concept implementation at https://reviews.llvm.org/D37921 <https://reviews.llvm.org/D37921>.
>>
>> The main change is that since in the lambda the remark is now returned by value, we need to preserve its type in the insertion operator. This requires making the insertion operator generic. I am also curious if people see C++ portabilit...