search for: 5k6wsp

Displaying 5 results from an estimated 5 matches for "5k6wsp".

2017 Jul 20
8
[RFC] Add IR level interprocedural outliner for code size.
...ts). This would likely lead to an increase in compile time but should remain less than the baseline. * Non Exact Functions: The outliner currently ignores functions that do not have an exact definition. -- -- * CSiBE(Code Size Benchmark): www.csibe.org * More detailed performance data: goo.gl/5k6wsP * Implementation: https://github.com/River707/llvm/blob/outliner/lib/Transforms/IPO/CodeSizeOutliner.cpp -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170720/8733497e/attachment.html>
2017 Jul 22
4
[RFC] Add IR level interprocedural outliner for code size.
...LTO numbers as well. Thanks, River Riddle On Sat, Jul 22, 2017 at 3:23 PM, Andrey Bokhanko <andreybokhanko at gmail.com> wrote: > Hi River, > > Very impressive! -- thanks for working on this. > > A few questions, if you don't mind. > > First, on results (from goo.gl/5k6wsP). Some of them are quite > surprising. In theory, "top improvements" should be quite similar in all > three approaches ("Early&Late Outlining", "Late Outlining" and "Machine > Outliner"), with E&LO capturing most of the cases. Yet, they are v...
2017 Jul 21
2
[RFC] Add IR level interprocedural outliner for code size.
...hould remain less > than the baseline. > > * Non Exact Functions: The outliner currently ignores functions that do > not have an exact definition. > > -- -- > > * CSiBE(Code Size Benchmark): > > www.csibe.org > > * More detailed performance data: > > goo.gl/5k6wsP > > * Implementation: > > https://github.com/River707/llvm/blob/outliner/lib/Transforms/IPO/ > CodeSizeOutliner.cpp > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170721/e82cbbc5/att...
2017 Jul 31
2
[RFC] Add IR level interprocedural outliner for code size.
...t in-tree it would be appropriate to ask for a comparative analysis against the existing pass. How is this different? The real question comes from what exactly you want to define as a "comparative analysis". When posting the patch I included additional performance data( found here goo.gl/5k6wsP<http://goo.gl/5k6wsP>) that includes benchmarking and comparisons between the outliner that I am proposing and the machine outliner on a wide variety of benchmarks. The proposed outliner performs quite favorable in comparison. As for feature comparison, the proposed outliner has many features...
2017 Jul 29
7
[RFC] Add IR level interprocedural outliner for code size.
Apologies for delayed joining of this discussion, but I had a few notes from this thread that I really wanted to chime in about. River, I don't mean to put you on the spot, but I do want to start on a semantic issue. In several places in the thread you used the words "we" and "our" to imply that you're not alone in writing this (which is totally fine), but your