asmjit VS ChrysaLisp

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.

Inspired by the TaOS Virtual Processor[0]:

"ChrysaLisp is a 64-bit, MIMD, multi-CPU, multi-threaded, multi-core, multi-user parallel operating system with features such as a GUI, terminal, OO Assembler, class libraries, C-Script compiler, Lisp interpreter, debugger, profiler, vector font engine, and more. It supports MacOS, Windows, and Linux for x64, Riscv64 and Arm64 and eventually will move to bare metal. It also allows the modeling of various network topologies and the use of ChrysaLib hub_nodes to join heterogeneous host networks. It has a virtual CPU instruction set and a powerful object and class system for the assembler and high-level languages. It has function-level dynamic binding and loading and a command terminal with a familiar interface for pipe-style command line applications. A Common Lisp-like interpreter is also provided."[1]

More HN discussion, with links to more discussion[2].

[0] https://news.ycombinator.com/item?id=9806607

[1] https://github.com/vygr/ChrysaLisp

[2] https://news.ycombinator.com/item?id=34415936

Thanks, this saved me some time. I was just debugging why the project I work on (LibHunt) hadn't logged the mention of https://github.com/vygr/ChrysaLisp on this post... the reason being - you've updated the URL after it was submitted.

I'll give another OS project to contribute to where the developers will help you a lot with your understanding of OS development: https://github.com/vygr/ChrysaLisp

One of the projects I've enjoyed working on in the past is: ChrysaLisp OS/Lang

It’s no grand work of coding but: https://github.com/vygr/ChrysaLisp/lib/date/date.inc

ChrysaLisp is portable assembler in () more than Lisp - any other Lisp system wouldn't have comments about clobbering registers.