Our great sponsors
qbe-rs | c4 | |
---|---|---|
29 | 11 | |
66 | 9,212 | |
- | - | |
3.3 | 0.0 | |
8 months ago | 4 months ago | |
Rust | C | |
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.
qbe-rs
-
Odin Programming Language
> I think it uses a different backend than LLVM
harec uses https://c9x.me/compile/
-
Frontend for GCC?
Have you considered QBE?
- QBE – Compiler Back End
-
What do C programmers think of the Zig language in 2023?
I really hope other new projects (like QBE) can really grow and become widely used
-
Toy C compiler, worth having an IR stage?
I really liked targetting QBE (https://c9x.me/compile/) as an IR, as it gave me lots of back-end optimisations for free 😊.
-
C or LLVM for a fast backend?
There is: QBE.
-
A whirlwind tour of the LLVM optimizer
You might be underestimating the accuracy of the CPU models LLVM uses.
For x86, the same data the code generator uses drives llvm-mca[1], which given a loop body can tell you the throughput, latency, and microarchitectural bottlenecks (decoding, ports, dependencies, store forwarding, etc.)—if not always precisely, then still not worse then IACA, the tool written at Intel by people who presumably knew how the CPUs work, unlike LLVM contributors and the rest of us who can only guess and measure. This separately for Haswell, Sandy Bridge, Skylake, etc.; not “x86”.
Now, is this the best model you can get? Not exactly[2], but it’s close enough to not matter. Do we often need machine code to be optimized to that level of detail? Perhaps not[3], and with that in mind you can shave at least a factor of ten off LLVM’s considerable bulk at the cost of 20—30% of performance[4,5]. But if you do want those as well, it seems that the complexity of LLVM is a fair price, or has the right order of magnitude at least.
(Frontend not included, C++ frontend required to bootstrap sold separately, at a similar markup compared to a C-only frontend with somewhat worse ergonomics.)
[1] https://llvm.org/docs/CommandGuide/llvm-mca.html
[2] https://www.uops.info/
[3] https://briancallahan.net/blog/20211010.html
[4] https://c9x.me/compile/
[5] https://drewdevault.com/talks/qbe.html
-
Made my first LLVM front-end… Now what?
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)?
-
Rust port of B3 from WebKit, LLVM-like backend
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.
c4
- A tiny hand crafted CPU emulator, C compiler, and Operating System
-
Running the "Reflections on Trusting Trust" Compiler
The C4 compiler [https://github.com/rswier/c4] is a self-hosting compiler for a subset of the C programming language that produces executable x86 code. You can understand and audit this code in a couple of hours (its 528 lines).
It could be an interesting exercise to bootstrap up from something like this to a working linux environment based solely on source code compilation : no binary inputs. Of course a full linux environment has way too much source code for one person or team to audit, but at least it rules out RoTT style binary compiler contamination.
- C4: C in Four Functions
- AoikC4x86Study: Line-by-line comments to c4.c and c4x86.c files
-
Flattening ASTs (and Other Compiler Data Structures)
I was surprised to see nodes still have two pointers ("references") given that you now know that that the first pointer will always point exactly to the next node. I've see https://github.com/rswier/c4 use that. Granted it doesn't make for the most readable code, but it's even smaller and faster.
-
vermin_vm: Virtual Machine(~400 lines) + Assembler(~800 lines) written in C
VMs with simple instruction sets is a fun topic. Some years ago I got inspired by the amazing rswier/c4 compiler by Robert Swierczek and explored the smallest instruction set I could get away with to create VMs that could run non-trivial workloads.
-
Hand-optimizing the TCC code generator
C4 comes to mind (C in 4 functions), https://github.com/rswier/c4.
have you considered adding a backend for LLVM? perhaps a bit heavyweight, but it could be a good way to get C/C++, fortran, rust, etc. if that's something you'd like!
-
Some people of the Linux Community in a nutshell
I use Alpine Linux (no GNU bloat btw), dwm (Sucks less!), and I edit all my C (no bloat language) through busybox ed and compile my programs with (c4)[https://github.com/rswier/c4]
-
which programming language was used to make c++ compiler?
Keep in mind you can create a "usable" C compiler by yourself, and is doable in surprisingly low amount of code. Try https://github.com/rswier/c4/blob/master/c4.c
- What is the simplest self-compiling subset of C?
What are some alternatives?
ubpf - Userspace eBPF VM
stage0 - A set of minimal dependency bootstrap binaries
mir - A lightweight JIT compiler based on MIR (Medium Internal Representation) and C11 JIT compiler and interpreter based on MIR
bcompiler - Mirror of http://www.rano.org/bcompiler.tar.gz, with a bootstrap script
minivm - A VM That is Dynamic and Fast
libcperciva - BSD-licensed C99/POSIX library code shared between tarsnap, scrypt, kivaloo, spiped, and bsdiff.
well - The Future of Assembly Language. https://wellang.github.io/well/
fpga_craft - A voxel game/Minecraft clone for the iCE40 UP5K FPGA
wasmtime - A fast and secure runtime for WebAssembly
packedjson - packedjson is an alternative Nim implementation for JSON. The JSON is essentially kept as a single string in order to save memory over a more traditional tree representation.
Befunge - lang befunge 93 fast
cproc - C11 compiler (mirror)