News for hackers. Stuff that matters.
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by omginternets on Thursday October 29, 2015 @09:36AM (#10470837)
Guys, what's a "trace optimizer"? Google is failing me by returning results about MySQL.
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by pramodliv1 on Thursday October 29, 2015 @09:42AM (#10470880)
Search https://www.google.com?q=trace+optimizer+compilers

According to wikipedia: https://en.wikipedia.org/wiki/Tracing_just-in-time_compilati...

Tracing just-in-time compilation is a technique used by virtual machines to optimize the execution of a program at runtime. This is done by recording a linear sequence of frequently executed operations, compiling them to native machine code and executing them. This is opposed to traditional just-in-time (JIT) compilers that work on a per-method basis.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by Nyetan on Thursday October 29, 2015 @09:42AM (#10470883)
They're referring to a tracing JIT[1], I believe.

[1]:https://en.wikipedia.org/wiki/Tracing_just-in-time_compilati...

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by shellac on Thursday October 29, 2015 @09:46AM (#10470915)
I assume it's a reference to tracing JIT (https://en.wikipedia.org/wiki/Tracing_just-in-time_compilati...).

It's a JIT that traces runtime execution, rather than looking at whole method or function bodies. In particular it eliminates control flow, which simplifies optimisation.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by DasIch on Thursday October 29, 2015 @10:58AM (#10471487)
Traces are an artifact produced by some JITs.

Basically you observe loops and loops that satisfy certain criteria are traced, that is all operations performed within one iteration are stored. Such a trace is then optimized, compiled to machine code and then executed for every iteration when the loop is encountered again.