On Fri, 16 Oct 2015 16:43:54 +0100 Tom Hacohen <t...@osg.samsung.com> said:
> > See the code, it was already used only once, so it was not actually > > reused at all. Since this is code in the header, this could have never > > been changed without breaking ABI anyway, which means this change > > actually has 0 performance impact. Well, actually, it is a slight > > positive impact, as you now pass less things on the stack and the "code > > size" is a bit smaller. > > > > I'm working on a follow up patch that improves speed drastically that > > actually caches some values among calls. I already finished and it's > > pretty awesome, but I need to just see if I can improve it a bit further > > before I push. I guess I can puhs now and worst can improve in a > > separate patch. > > There you go, now it's in. This should be the end of this series of ABI > breaks and hopefully the end of ABI breaks in Eo in general. This was > requested by Carsten so all of the ABI breaks that lead to significant > performance improvements will be in now. > > I have a few more improvements in my branch, and I think I reach a total > of around 30% speed improvement with my whole patch series. I plan on > maybe doing a quick write up with some graphs and more info soon. where is your benchmark tool/thingy you use for this? -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
