Our great sponsors
- ONLYOFFICE ONLYOFFICE Docs — document collaboration in your environment
- InfluxDB - Access the most powerful time series database as a service
- CodiumAI - TestGPT | Generating meaningful tests for busy devs
- SonarQube - Static code analysis for 29 languages.
|5 months ago||10 months ago|
|GNU General Public License v3.0 or later||GNU General Public License v3.0 only|
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Made my first LLVM front-end… Now what?
2 projects | reddit.com/r/Compilers | 9 May 2023
You can try buildling you own backend like llvm. A good example or starting point is probably QBE since it is extremely small but very functional.
Best book on writing an optimizing compiler (inlining, types, abstract interpretation)?
8 projects | reddit.com/r/ProgrammingLanguages | 17 Apr 2023
Rust port of B3 from WebKit, LLVM-like backend
2 projects | reddit.com/r/ProgrammingLanguages | 14 Apr 2023
How big is the whole backend? I've heard that it is small but I wanted to compare it to QBE which is around 8 KLoC and it is quite interesting too.
Few lesser known tricks, quirks and features of C
2 projects | news.ycombinator.com | 19 Feb 2023
I think QBE might be what you're looking for?
Do you consider LLVM a complicated software? And are there any alternatives and how they compare to LLVM?
As far as I know, there is QBE, which is actually kinda underrated, and Cranelift, mainly designed for JIT compilation
Before that, I had spent a bit of time working with QBE, which is much simpler and really easy to write a frontend for. I switched to libgccjit though, because I got frustrated with a few of the things lacking from QBE (like the ability to easily keep track of where different variables live on the stack). I think for many hobby language projects, QBE would be a good option (my project was off the ground very fast using QBE, and I got pretty far before I ran into limitations I couldn't easily work around).
If one of your parameters is size/complexity of the backend and you prefer something smaller, have a look at qbe and cwerg
The alternatives are generally hidden inside of another compiler. The big exception seems to be qbe (https://c9x.me/compile/) however since the author appears to have written this code without peer review, it's not easy to read it's source code.
Smallest possible self-hosting zig compiler
4 projects | reddit.com/r/Zig | 7 Dec 2022
So my question is this: if a backend like QBE (~12k Loc) was added to Zig and Zig only had to compile Zig code (no C, etc) for that QBE backend -- about how many LoC would that Zig need to be?
Building the fastest Lua interpreter.. automatically
8 projects | news.ycombinator.com | 22 Nov 2022
GCC is written in C++ these days, so something like QBE(https://c9x.me/compile/) would be needed.
Do transpilers just use a lot of string manipulation and concatenation to output the target language?
4 projects | reddit.com/r/ProgrammingLanguages | 27 May 2023
Ask HN: Admittedly Useless Side Projects?
21 projects | news.ycombinator.com | 24 Jun 2022
- https://github.com/rochus-keller/Smalltalk/ Parser, code model, interpreter and navigable browser for the original Xerox Smalltalk-80 v2 sources and virtual image file
- https://github.com/rochus-keller/Som/ Parser, code model, navigable browser and VM for the SOM Smalltalk dialect
- https://github.com/rochus-keller/Simula A Simula 67 parser written in C++ and Qt
> do you regret those endeavours?
No, not in any way; the projects were very entertaining and gave me interesting insights.
Ask HN: Recommendation for general purpose JIT compiler
12 projects | news.ycombinator.com | 15 May 2022
If your DSL is statically typed then I recommend that you have a look at the Mono CLR; it's compatible with the ECMA-335 standard and the IR (CIL) is well documented, even with secondary literature.
If your DSL is dynamically typed I recommend LuaJIT; the bytecode is lean and documented (not as good as CIL though). LuaJIT also works well with statically typed languages, but Mono is faster in the latter case. Even if it was originally built for Lua any compiler can generate LuaJIT bytecode.
Both approaches are lean (Mono about 8 MB, LuaJIT about 1 MB), general purpose, available on many platforms and work well (see e.g. https://github.com/rochus-keller/Oberon/ and https://github.com/rochus-keller/Som/).
When is Smalltalk's speed an issue?
2 projects | reddit.com/r/smalltalk | 21 Feb 2022
At the latest when you run a benchmark suite like Are-we-fast-yet; here are some measurment results: http://software.rochus-keller.info/are-we-fast-yet_crystal_lua_node_som_pharo_i386_results_2020-12-29.pdf. See also https://github.com/rochus-keller/Som/ and https://github.com/rochus-keller/Smalltalk.
LuaJIT for backend?
6 projects | reddit.com/r/ProgrammingLanguages | 2 Jan 2022
LuaJIT is well suited as a backend/runtime environment for custom languages; I did it several times (see e.g. https://github.com/rochus-keller/Smalltalk, https://github.com/rochus-keller/Som/, https://github.com/rochus-keller/Oberon/). I also implemented a bit of infrastructure to ease the reuse: https://github.com/rochus-keller/LjTools. LuaJIT has some limitations though; if you require closures you have to know that the corresponding LuaJIT FNEW bytecode is not yet supported by the JIT, i.e. switches to the interpreter; as a work-around I implemented my own closures; LuaJIT also doesn't support multi-threading, but co-routines; and there is no debugger, and the infrastructure to implement one has limitations (i.e. performance is low when running to breakpoints). For most of my projects this was no issue. Recently I switched to CIL/Mono for my Oberon+ implementation which was a good move. But still I consider LuaJIT a good choice if you can cope with the mentioned limitations. The major advantage of LuaJIT is the small footprint and impressive performance for dynamic languages.
Optimizing an old interpreted language: where to begin?
3 projects | reddit.com/r/Compilers | 4 May 2021
JITted lang which is faster than C?
6 projects | reddit.com/r/ProgrammingLanguages | 12 Feb 2021
This is a completely different kind of measurement; unfortunately this is not clear enough from my Readme. I wanted to find out, how well my naive Bluebook interpreter performs on LuaJIT (using my virtual meta tracing approach) compared to Cog, which is a dedicatd Smalltalk VM optimized with whatever genious approaches over two decades (or even longer considering the long experience record by Elliot). This experiment continues in https://github.com/rochus-keller/Som, because I didn't want to modify the original Smalltalk image. I found that my naive LuaJIT based approach is about factor seven behind the highly optimized Cog/Spur, and further improvements would require similar optimization tricks as in the latter.
What are some alternatives?
minivm - A VM That is Dynamic and Fast
ubpf - Userspace eBPF VM
Oberon - Oberon parser, code model & browser, compiler and IDE with debugger
Smalltalk - Parser, code model, interpreter and navigable browser for the original Xerox Smalltalk-80 v2 sources and virtual image file
mir - A lightweight JIT compiler based on MIR (Medium Internal Representation) and C11 JIT compiler and interpreter based on MIR
Shiori - Simple bookmark manager built with Go
Befunge - lang befunge 93 fast
rockstar - Makes you a Rockstar C++ Programmer in 2 minutes
simplelanguage - A simple example language built using the Truffle API.