On Tue, Jul 1, 2014 at 7:52 PM, Jason Orendorff <[email protected]> wrote:
> The proposed implementation technique underlying this is bytecode > instrumentation. One reason for this is that we already have tons of > practice > adding new opcodes to Ion, baseline, and the interpreter. We already know > how > to make them work the same in all modes and fast in Ion. Of course the > implementation technique could vary per event. If we choose to support an > event > that already has a natural choke-point in C++, we would not need bytecode > instrumentation to intercept that event. It is also true that bytecode > instrumentation has a few weaknesses--things like exception handling are > not > done by executing bytecodes at all. > Isn't this exactly what tracelogging does? Or, a subset of what tracelogging does, rather? _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
