On 02/06/2015 01:20 AM, Shu-yu Guo wrote:
I recently landed bug 1030389 to track the high-level optimizations
decisions
(i.e., deciding what MIR is emitted) made by IonBuilder. This information
will feed into the profiler and is attached to sampled JIT frames.
Not all optimization decisions are taken by IonBuilder, is there plan to
make this API available to other transformation phases. In particular, I am
thinking of Escape Analysis / GVN & LICM / Sink.
That's it! Instrumentation bugs also make great first bugs, and I would be
happy to mentor.
That's Great!
Should we instrument every code path, or only instrument the code path which
have big cliff?
--
Nicolas B. Pierron
_______________________________________________
dev-tech-js-engine-internals mailing list
dev-tech-js-engine-internals@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals