ts-native VS asmjit

I have gone through 3 iterations and the third was faster than Lua and came close (enough for me) to native C performance with the benchmarks I tried. I'm now on the fourth and hopefully last iteration of this masochistic quest and I'm tired. I want to do this right. I've even made it through much of the dragon book. Apart from the naive solutions I end up wanting to replace in each previous iteration, the problem I keep coming up against is that I can't find many resources that describe interfaces between the host (C++) and the compiled code. I come up with my own ideas for how things should work and look, and then once I finish I can't shake the feeling that there's a better/cleaner/faster way. I start over and come up with better solutions only to feel the same eventually. I want to write solid code that I can feel confident about so I can put this all behind me.

Here's an example: test.gjs

Some other instruction sets in some JSON: https://github.com/asmjit/asmjit/tree/master/db

The attentive reader may notice that this code is from a third-party library. So, we didn't want to include it in the article at first. However, we found something interesting. In 2017, somebody opened an issue in the asmjit project: the GCC 7.2 compiler issued a warning to the code above. The project authors fixed it:

You can use something like https://asmjit.com/ to generate and call x64 code at runtime.

But an easy to create a JIT would be to use https://github.com/asmjit/asmjit, which is used in RPCS3.

You could go the way of https://asmjit.com (or forth) and make it your assembler DSL on top of the low-level call.

But if you're willing to get closer to the hardware is https://github.com/bitfunnel/nativejit/ and https://asmjit.com/

https://github.com/asmjit/asmjit is nice. But using a JIT seems like a sledgehammer working around a lacking design.