Displaying 4 results from an estimated 4 matches for "r351892".
Did you mean:
r351894
2019 Jan 26
2
Status update on the hot/cold splitting pass
...by 2% across the entire iOS shared cache.
# Recent/ongoing work
Aditya and Sebastian contributed the hot/cold splitting pass in September 2018 (r341669). Since then, work on the pass has continued steadily. It gained the ability to extract larger cold regions (r345209), compile-time improvements (r351892, r351894), and a more effective cost model (r352228). With some experimentation, we found that scheduling splitting before inlining gives better code size results without regressing memory locality (r352080). Along the way, CodeExtractor got better at handling debug info (r344545, r346255), and a f...
2019 Jan 28
2
Status update on the hot/cold splitting pass
...ire iOS shared cache.
>
> # Recent/ongoing work
>
> Aditya and Sebastian contributed the hot/cold splitting pass in September 2018 (r341669). Since then, work on the pass has continued steadily. It gained the ability to extract larger cold regions (r345209), compile-time improvements (r351892, r351894), and a more effective cost model (r352228). With some experimentation, we found that scheduling splitting before inlining gives better code size results without regressing memory locality (r352080). Along the way, CodeExtractor got better at handling debug info (r344545, r346255), and a f...
2019 Feb 05
2
Status update on the hot/cold splitting pass
...d cache.
>
> # Recent/ongoing work
>
> Aditya and Sebastian contributed the hot/cold splitting pass in September
> 2018 (r341669). Since then, work on the pass has continued steadily. It
> gained the ability to extract larger cold regions (r345209), compile-time
> improvements (r351892, r351894), and a more effective cost model (r352228).
> With some experimentation, we found that scheduling splitting before
> inlining gives better code size results without regressing memory locality
> (r352080). Along the way, CodeExtractor got better at handling debug info
> (r34454...
2019 Feb 05
2
Status update on the hot/cold splitting pass
...Recent/ongoing work
>>
>> Aditya and Sebastian contributed the hot/cold splitting pass in September
>> 2018 (r341669). Since then, work on the pass has continued steadily. It
>> gained the ability to extract larger cold regions (r345209), compile-time
>> improvements (r351892, r351894), and a more effective cost model (r352228).
>> With some experimentation, we found that scheduling splitting before
>> inlining gives better code size results without regressing memory locality
>> (r352080). Along the way, CodeExtractor got better at handling debug info...