(In reply to comment #0) > * Handling both x86 and x64 boxing formats Will boxing formats differ from what we already have? Will ARM continue to use the same (64-bit) format as x86? Is there a work-in-progress IR design somewhere that I could look at? It'd be interesting to see if there's anything that might restrict or benefit performance on ARM, before it all gets integrated and hard to change.
(In reply to comment #1) > Will boxing formats differ from what we already have? Will ARM continue to > use the same (64-bit) format as x86? The boxing format may change for x64 but I don't think there are any plans for ARM/x86. It seems hard to change on 32-bit CPUs without re-introducing heap doubles. That actually might not be too bad, but it's a huge change (Luke says) because a bunch of infallible functions would need to become fallible. > Is there a work-in-progress IR design somewhere that I could look at? It'd > be interesting to see if there's anything that might restrict or benefit > performance on ARM, before it all gets integrated and hard to change. I'll get a user repo link up shortly. I've been offline for about a week and am picking up where I left off now. It's at the point where it can recover SSA from the bytecode, with basic control-flow (if branches, do/while loops). Now the next step is figuring out how to generate code off the new IR which entails a few major design pieces: * How local type inference and representation decisions work * How registers should be assigned to inputs and outputs * How values are held in the IR, unboxed and boxed as necessary * Whether we should lower the new MIR to a second, lower-level IR
repo up: http://hg.mozilla.org/users/danderson_mozilla.com/ionmonkey Immediate tasks are some more refactorings and getting it to generate some JIT code.