Slowly, systems programming languages are getting better in the sense of giving more guarantees and automating what can be automated without downsides.
Rust is one of the more promising system programming languages. Its central advantage is that it enforces memory safety and thread safety at compile time, without incurring any runtime overhead.
The part that enforces memory safety is called "the borrow checker".
It has been a long-standing tradition to develop a language far enough to be able to write the language's compiler in the same language, and Rust does the same. Rust is nowadays written in Rust.
We've tracked down the earlier Rust versions, which were written in OCaml, and were planning to use these to bootstrap Rust. But in parallel, John Hodge (Mutabah) developed a Rust compiler, called "mrustc", written in C++.
mrustc is now good enough to compile Rust 1.19.0.
Using mrustc, we were able to build Rust entirely from source with a bootstrap chain like this:
firstname.lastname@example.org ^ | email@example.com ^ | firstname.lastname@example.org ^ | email@example.com ^ | firstname.lastname@example.org ^ | email@example.com ^ | firstname.lastname@example.org ^ | email@example.com ^ | firstname.lastname@example.org ^ | email@example.com ^ | firstname.lastname@example.org ^ | g++
mrustc currently does no borrow checking -- so memory safety of our email@example.com is mostly guaranteed in the sense of "someone else built firstname.lastname@example.org using another Rust compiler and thus ran the borrow checker already".
The bootstrap chain is rather long. There are plans to extend mrustc to support newer Rust, but it turned out to be difficult.
Rust takes reproducible builds seriously, but there are some reproducibility problems left in earlier compilers that pop up very sporadically (mostly because of LLVM, and some because of Rust hashtable poisoning). Help wanted, especially from LLVM people!
Each target we want to support has to have support in LLVM, AND mrustc needs to have a specification of the alignment and sizes of the base types.
About GNU Guix
GNU Guix is a transactional package manager for the GNU system. The Guix System Distribution or GuixSD is an advanced distribution of the GNU system that relies on GNU Guix and respects the user's freedom.
In addition to standard package management features, Guix supports transactional upgrades and roll-backs, unprivileged package management, per-user profiles, and garbage collection. Guix uses low-level mechanisms from the Nix package manager, except that packages are defined as native Guile modules, using extensions to the Scheme language. GuixSD offers a declarative approach to operating system configuration management, and is highly customizable and hackable.
GuixSD can be used on an i686, x86_64, ARMv7, and AArch64 machines. It is also possible to use Guix on top of an already installed GNU/Linux system, including on mips64el and aarch64.
This post does not yet carry an agreed-upon license.
Tópicos relacionados:Bootstrapping Reproducible builds Security
Unless otherwise stated, blog posts on this site are copyrighted by their respective authors and published under the terms of the CC-BY-SA 4.0 license and those of the GNU Free Documentation License (version 1.3 or later, with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts).