vermin_vm
c4
| vermin_vm | c4 | |
|---|---|---|
| 3 | 11 | |
| 6 | 9,353 | |
| - | - | |
| 1.1 | 0.0 | |
| about 1 year ago | 5 months ago | |
| C | C | |
| MIT License | 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.
vermin_vm
-
vermin_vm: Virtual Machine(~400 lines) + Assembler(~800 lines) written in C
git clone https://github.com/Jaysmito101/vermin_vm cd vermin_vm cmake -S ./ -B ./build cmake --build ./build ```
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?
rwisa-vm - VM implementations for the RW instructions set architecture
stage0 - A set of minimal dependency bootstrap binaries
bcompiler - Mirror of http://www.rano.org/bcompiler.tar.gz, with a bootstrap script
qbe-rs - QBE IR in natural Rust data structures
libcperciva - BSD-licensed C99/POSIX library code shared between tarsnap, scrypt, kivaloo, spiped, and bsdiff.
fpga_craft - A voxel game/Minecraft clone for the iCE40 UP5K FPGA
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.
cproc - C11 compiler (mirror)
jsonpak - Packed ASTs for compact and efficient JSON representation, with JSON Pointer, JSON Patch support.
neat - The Neat Language compiler. Early beta?
Befunge - lang befunge 93 fast
bamboomigrate - bamboomigrate is a typelevel transformation and migration library