On 02/05/2014 10:09 PM, Boris Zbarsky wrote:
JIT Inspector is a pretty awesome tool, but it's bitrotted slightly...
In particular:
1) It doesn't seem to know anything about baseline.
2) I've had a hard time making parts of it other than "Ion Activity"
work.
Is there any interest in updating it to deal with the current state of
the world?
I don't know that JIT inspector work should block on this, but one way
forward that we're pursuing is to make Debugger not disable IonMonkey
(basically, to only de-optimize to the extent necessary for what
Debugger has actually been asked to do --- just collecting dumb stack
traces shouldn't de-optimize anything, for example), and then expose JIT
optimization data on Debugger. Why have two mechanisms for inspecting
your running program, when Debugger has a lot of the stuff you'd want
anyway?
This has been Shu's initiative; he especially wants to use Debugger to
report failure to parallelize in PJS constructs.
_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
