JIT frame pre-proposal

[Jason E. Aten]

I've been working on a JIT compiler in Go, with embedded game

scripting as my mental model. 

If you are aware of https://github.com/libriscv/libriscv then

my project is similar. It needs high performance foreign code interop.

I want a 2 nanosecond CALL/RET path rather than a 43 nanosecond CGO switch.

I looked at the recent https://github.com/golang/go/issues/78189

but I feel it is super complicated, with a huge API surface, while also not being general enough.

I've drafted up a spec for a self-describing foreign JIT stack-frame protocol. I'd appreciate any early feedback before I implement/file a real proposal. See the attached markdown. It has a pretty small additional API surface. Most of the complexity burden is shifted to the JIT author.

Thanks for your thoughts.

Jason

[Jason E. Aten]

If you prefer to read markdown as a github gist, here is a link. 

https://gist.github.com/glycerine/e434537e10c0e630032c3ab57b0247e8