@pcwalton @iSH_app While constrained slightly differently (OSR requirements, usually tiered up to a JIT, etc.) JavaScript engine bytecodes are probably what you want to look at. Some certainly look a bit like what you’ve described.
@pcwalton @iSH_app For @iSH_app compatibility is very important, so the frontend is probably always going to accept an ISA with actual software compiled against it (and, soon, we’ll be limited to ones supported by Linux).
@pcwalton @iSH_app We emulate x86 on x86_64/arm64 so the interpreter is able to pin all the registers, at least: github.com/ish-app/ish/bl…. So we get that “for free”, at least. The instructions are still annoying to decode, though, so we cache those.
@pcwalton @iSH_app I’m not sure if that cache rises to the level of what you could reasonably call “bytecode”, but making the interpreter faster would probably require a proper one that could be used as an IR for optimizations. I suspect that it might look similar to what you’re describing.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
