Re:Stoke – A stochastic superoptimizer and program synthesizer
by sanxiyn on Friday May 29, 2020 @07:17AM
(#23348635)
STOKE proves full equivalence.
[ Parent
| on HN ]
Re:Stoke – A stochastic superoptimizer and program synthesizer
by TheOtherHobbes on Friday May 29, 2020 @09:19AM
(#23349636)
Of trivial code blocks.
That's not a terrible goal if you want to make key libraries faster and more efficient.
But I'm unconvinced that it would be easy to scale up these techniques to auto-clone and improve a big application like Photoshop or Word - or even a generic CRUD app.
Re:Stoke – A stochastic superoptimizer and program synthesizer
by jcranmer on Friday May 29, 2020 @01:14PM
(#23352658)
This is basically doing what compiler engineers call peephole optimization: optimizing small windows of code, which is a standard part of the optimizer pipeline.
One advantage of peephole optimization is that pretty much all code is amenable to it, so it doesn't rely on their being one key, hot loop to optimize to see performance gains. The main disadvantage is that gains in peephole optimization tend to be quite small, so you're combing for single-digit percentage speedups.
Re:Stoke – A stochastic superoptimizer and program synthesizer
by naasking on Friday May 29, 2020 @10:05AM
(#23350076)
Even big applications are composed of trivial code blocks. The optimisations are probably synergistic with other passes, and would probably expose many inlining opportunities that didn't exist before.