mescc-tools-seed
c4
Our great sponsors
mescc-tools-seed | c4 | |
---|---|---|
8 | 11 | |
85 | 9,212 | |
- | - | |
6.6 | 0.0 | |
2 months ago | 4 months ago | |
C | C | |
GNU General Public License v3.0 only | 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.
mescc-tools-seed
- Running the "Reflections on Trusting Trust" Compiler
- stage0 x86 seed reduced from 357 Bytes to 256 Bytes
-
test
From here I found a reference to the Gash, Mes-M2 and stage0 projects, who's README.org references a nice wiki for stage0. The Wiki references a more expansive stage0-posix repo. From here, I finally got all the pieces to fit togeather.
-
How reproducible are Guix packages?
Of course, reproducible builds will only give you security if you trust the compiler you're using to verify. Unlike traditional distributions, Guix packages are rigorously defined in terms of their dependencies all the way down to ~60 MB of bootstrap binaries. There has been a lot of cool work to reduce the initial binary seed size, and they are working to reduce this even further to a "full source" bootstrap which will make use of the stage0 project to bootstrap the entire OS from a small, auditable ASCII Hex -> binary program.
-
stage0-posix was ported to RISC-V
stage0-posix just gained initial support for RISC-V (64-bit). It starts with 392 byte hex assembler, 361 byte "shell" and bootstraps simple linker (hex2), macro assembler (M0). Then it builds cc_riscv64 RISC-V compiler written in RISC-V assembly and uses it to build simple C compiler written in C (M2-Planet). Then it builds a few extra utilities (cp, mkdir, untar, ungz, sha256sum, chmod)
-
Bootstrapping from Hex to Bison to GCC
I wonder if Brainfuck could be used for https://github.com/oriansj/stage0-posix ? It would not surprise me if there is no other language for which there are so many interpreters written in so many different programming languages. It is even possible to write a Brainfuck interpreter in Brainfuck, which can be verified. And there is also a Brainfuck interpreter written in x86-64: https://github.com/316k/brainfuck-x86-64 . It is a little larger than hex0_x86.hex0 , but not too much to make it hard to verify.
-
A Brief Introduction to Forth (1993)
I'd argue the easiest to implement language is macro-assembly then the C subset known as cc_x86
https://github.com/oriansj/mescc-tools-seed
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?
live-bootstrap - Use of a Linux initramfs to fully automate the bootstrapping process
stage0 - A set of minimal dependency bootstrap binaries
mes-m2 - Making Mes.c M2-Planet friendly
bcompiler - Mirror of http://www.rano.org/bcompiler.tar.gz, with a bootstrap script
archlinux-installer-script - Arch Linux install script. Only performs the minimal steps for booting into arch. 75 lines of script with full progress messages and tutorial.
qbe-rs - QBE IR in natural Rust data structures
neat - The Neat Language compiler. Early beta?
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
bootstrap-seeds - The roots of trust for all architectures
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.