On Thu, Apr 28, 2016 at 10:35 PM, Nicolas B. Pierron
<[email protected]> wrote:
>
> For the JIT, what would improve our life a lot, would be if we could dump
> the code of the compiled function which is currently being executed. If we
> have that, I think we can make a tool to reverse engineer the trace of
> functions used to generate the assembly code, and potentially walk back to
> the LIR / Inline Cache which produced the code.
Good idea. How hard would this be? Should I file a bug?
> One idea I had, would be to make unit test for phases of the compiler.
> Unfortunately this is not something trivial to add as-is, and we would have
> to detail all the hidden assumptions which are currently present in all the
> phases.
>
> I think this would be something we should consider doing if we are going to
> rewrite the MIR representation / the compiler, as I expect to do as part of
> THM as its internal representation should be easy {de,}serialize.
Jakob is doing exactly this with Cretonne. I think clang has something
similar. It's definitely a good idea for any future IR forms.
(BTW, what is "THM"?)
Nick
_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
