simplelanguage VS asmjit

That sort of stuff is easy to do with Truffle (which, ironically, lets you define a language using what they call the "truffle dsl").

The SimpleLanguage tutorial language has a bigint style number scheme with efficient optimization:

https://github.com/graalvm/simplelanguage/blob/master/langua...

Truffle has no opinion on how you parse the sources. It cares about how you execute them from an intermediate Truffle guided representation produced by the parser.

In other words antlr and truffle are a great fit. We even use this pairing for our example language simplelanguage.

https://github.com/graalvm/simplelanguage

Do you have any feedback on how we could improve the docs? If so, please let us know!

I believe the easiest way to start a new Truffle language implementation is to fork SimpleLanguage [1] and turn it into your language. Did you try to do that?

[1] https://github.com/graalvm/simplelanguage

Finally, I would suggest you to take a look at the Truffle/GraalVM ecosystem(https://www.graalvm.org/graalvm-as-a-platform/language-implementation-framework/). The documentation is not exactly very elaborate, but a few good resources are Mumbler(http://cesquivias.github.io/blog/2014/10/13/writing-a-language-in-truffle-part-1-a-simple-slow-interpreter/#mumbler-language), SimpleLanguage(https://github.com/graalvm/simplelanguage), and (https://www.endoflineblog.com/graal-truffle-tutorial-part-4-parsing-and-the-trufflelanguage-class).

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.