elvm VS asmbf

ELVM lacks a lot of features, but serve the purpose of simplifying the creation of new frontends.

How does it work? Is it translating the C source code of the 8cc C compiler to lambda calculus?

So like C -> ELVM IR -> lambda calculus?

https://github.com/shinh/elvm

If so, it seems like 8cc is doing most of the heavy lifting

Interested parties should also check out awka (https://github.com/noyesno/awka) and ELVM (which can compile C into awk or sed, among various other things) (https://github.com/shinh/elvm)

Oh yeah, there's a compiler that can compile C to sed.

Would be interesting to have some small C program such as info-zip compiled to bf via ELVM [1] and do a speed comparison.

https://github.com/shinh/elvm

A C compiler that can output Malbolge (among many other esolangs) can be found at https://github.com/shinh/elvm - dunno if it has any relation to this work.

Note that the Malbolge (or rather LMAO/HeLL) backend was added back in July 2019, so I'm not so sure about their claim that "It's as of 2020 and 2021, the most advanced, usable Malbolge program ever created."

You are looking for ELVM: https://github.com/shinh/elvm/

Prepare yourself for asm2bf, the next generation target platform.

Basically, my toolchain is built on two separate projects. The first one is a low level assembler (that lays out code on instruction cycles, handles restoring things, etc.. - generally, very similar to how Malbolge works, except with the incredibly annoying parts such as manually encrypting the code or finding instruction cycles is), and the second one is a high level assembler.

I used my existing project called asm2bf: https://github.com/kspalaiologos/asmbf (feel free to check it out), as a base for the high level assembler. And the original Lisp has been written in a tweaked version of it.

Once I was done, I optimised the high level version, and then took the asm2bf compiler output and did a few optimisations manually on it (everything that my peephole optimisation didn't catch).