GNU Guix bootstraps itself using a mutual self-hosting scheme interpreter and C compiler! https://guix.gnu.org/blog/2019/guix-reduces-bootstrap-seed-by-50/
Related Posts
I've been experimenting with an 'evaluate up to cursor' mode for my PL project.
I love evaluating self-contained snippets in Lisp, this generalises the idea.
The interpreter remembers the arguments when you run tests, then can re-use them when you say 'eval up to here'.
What do you think?
I would have thought that invoking a C compiler would be a solved problem. Looking at Rust's cc crate there's a remarkable long tail of corner cases to fix.
Exotic CPUs, microarchitectures, compiler differences, operating system differences, etc.
https://github.com/rust-lang/cc-rs/blob/main/CHANGELOG.md
GNU Make defaults to a single worker, and newer build tools (e.g. ninja) default to the number of physical CPUs.I wish there was an option for 'leave me a little bit of my machine to do stuff'.