Yoakke VS Cwerg

A quick status update Not too long ago I've posted about a new library, Yoakke that we are developing as a tool to help compiler development with. The goal is to implement all the "crud" that compilers have usually, so the developer can concentrate on the language-specific stuff. Last time you couldn't even try out the library, as it wasn't released in some package manager. Fortunately, we now have nightly builds, which should let you experiment until the first official release!

Started out working on an x86 module for the Yoakke library.

And so, the Yoakke Compiler Infrastructure library was born. It’s still a young project with a gigantic roadmap ahead, but the first few components are already documented and testable. Its goal is to provide solutions that will fit for most cases, but lets you roll your own if you needed, while still getting some help along the way.

Perhaps these have already been dealt with and I'm missing critical information. If so, my apologies. Great work, in any case.

[1] https://github.com/robertmuth/Cwerg/tree/master/FrontEnd#dis...

Cwerg has backend that can be used as JIT and is written with readability in mind. Additional documentation can be found here: https://github.com/robertmuth/Cwerg/tree/master/Docs

I defined a basic ISA-like IR for Cwerg. It has unlimited registers and no constraints on immediates.

entire compiler front end ast nodes

I was also going down the path of bike shedding concrete syntax for my language Cwerg before pulling the plug on that effort and just using s-exprs. I managed to make the s-expr quite succinct by carefully choosing the order of arguments so I can omit optional ones. Also very helpful was to use square brackets for list, e.g. (call fun-name [arg1 arg2]). This simplifies parsing a little bit and is easier on the eye. Here are some Code Examples

I am iterating over the languages features for Cwerg's Frontend which aims to be a low level language with about the complexity of C but with some of the comforts of modern languages. I am especially happy with the choice of adding sum types. Relative to C the current feature set looks like this: Removed: * arrays decay to pointers * bitfields * separate compilation (more of a backend issue) * pre-processor * varargs * implcit type conversions * (untagged) unions * ++/-- * comma operator * implicitly nullable pointers * goto