search for: r352080

Displaying 4 results from an estimated 4 matches for "r352080".

Status update on the hot/cold splitting pass
2019 Jan 26
2
Status update on the hot/cold splitting pass
.... 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 few other issues in this utility were fixed (r348205, r350420). At this point, we're able to build & run our software stack with hot/cold splitting enabled. We’d like to introduce a CC1 option to saf...
Status update on the hot/cold splitting pass
2019 Jan 28
2
Status update on the hot/cold splitting pass
.... 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 few other issues in this utility were fixed (r348205, r350420). > > At this point, we're able to build & run our software stack with hot/cold splitting enabled. We’d like to introduce a CC1 opt...
Status update on the hot/cold splitting pass
2019 Feb 05
2
Status update on the hot/cold splitting pass
...ity 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 few other issues in this utility were fixed > (r348205, r350420). > > At this point, we're able to build & run our software stack with hot/cold > splitting enabled. We’d like to intro...
Status update on the hot/cold splitting pass
2019 Feb 05
2
Status update on the hot/cold splitting pass
...arger 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 few other issues in this utility were fixed >> (r348205, r350420). >> >> At this point, we're able to build & run our software stack with hot/cold >> splitting enabled...