On 12/12/2013 12:45 PM, Kannan Vijayan wrote: > Isn't part of the reason for that the fact that TraceMonkey (and with > Jaeger, Ion, and with Baseline, etc.) wasn't really a JS-specific > tree? They were jit-specific trees, and the jits generally have a lot > of cross-talk with the main JS VM.
No they weren't. We kept repurposing the names. You can't infer the purpose of the tree from the name. tracemonkey in particular was effectively js-inbound for a long time. > > I would expect far less overlap between "general browser work" and "JS > work" than between "JS non-jit work" and "JS jit work". I wouldn't. It depends on what you work on. I end up crossing the JS/browser boundary frequently. But I still think there's enough isolation that a js-inbound would work right now. _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
