zig-bootstrap
mrustc
zig-bootstrap | mrustc | |
---|---|---|
8 | 75 | |
332 | 2,087 | |
1.5% | - | |
7.1 | 8.8 | |
7 days ago | 6 days ago | |
C | C++ | |
- | MIT License |
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.
zig-bootstrap
-
Zig for Raspberry Pi 2 Model B
if you know what compiler target is used on your pi 2 you can probably get someone to cross compile it for you. https://github.com/ziglang/zig-bootstrap This should be reasonably easy to use.
-
Compiling Zig with Low RAM (16GB)?
Use Zig Bootstrap, it is easier. And It should work on 16gb.
-
compile zig based on llvm-14
you can cross compile for armv7a with zig-bootstrap
-
Zig is now self–hosted by default
They have a project for maintaining this: https://github.com/ziglang/zig-bootstrap
- Looking into Zig
-
[Discussion] I firmly believe a self hosted compiler is a huge security risk that *should not* be undertaken.
I think that's the purpose of the zig-bootstrap project. By having these dependencies installed: clang, llvm, python3, cmake (notice no zig) you end up with zig compiled.
-
Zig 0.8.0 Released!
The current state is that they offer a repo with LLVM and the stage1 (C++) compiler, which should build on any system that can build LLVM (so any system with a modern C++ compiler and build tools). Or you can grab the upstream Zig code and build it against regular LLVM 12 yourself using an existing LLVM 12 clang/etc stack.
- Zig 0.8.0 Release Notes
mrustc
-
Why do lifetimes need to be leaky?
No, you don't. Existential proof: mrustc ignores lifetimes. Just flat out simply ignores. It changes some corner-cases related to HRBT, yet rustc compiled by mrustc works (that's BTW mrustc exist: to bootsrap the rustc compiler).
-
I think C++ is still a desirable coding platform compared to Rust
Incidentally C++ is the only way to bootstrap rust without rust today.
https://github.com/thepowersgang/mrustc
-
Rust – Faster compilation with the parallel front-end in nightly
Well, there is mrustc[0], a Rust compiler that doesn't include a borrow-checker, so it's possible to compile (at least some versions of) Rust without a borrow checker, though it might not result in the most optimized code.
AFAIK there are some optimization like the infamous `noalias` optimization (which took several tries to get turned on[1]) that uses information established during borrow checking.
I'm also not sure what the relation with NLL (non-lexical lifetimes) is, where I would assume you would need at least a primitive borrow-checker to establish some information that the backend might be interested in. Then again, mrustc compiles Rust versions that have NLL features without a borrow-checker, so it's again probably more on the optimization side than being essential.
[0]: https://github.com/thepowersgang/mrustc
[1]: https://stackoverflow.com/a/57259339
- Running the "Reflections on Trusting Trust" Compiler
-
Forty years of GNU and the free software movement
> Maybe another memory safe language, but Rust has severe bootstrapping issues which is a hard sell for distros that care about source to binary transparency.
It is possible to bootstrap rustc from just GCC relatively easily, although it's a little bit time consuming.
You can use mrustc to bootstrap Rust 1.54: https://github.com/thepowersgang/mrustc
And from then you can go through each version all the way to the current 1.72. (Each new Rust version officially needs the previous one to compile.)
-
Building rustc on sparcv9 Solaris
Have you tried this route : https://github.com/thepowersgang/mrustc ?
-
GCC 13 and the state of gccrs
Mrustc supports Rust 1.54.0 today
- Any alternate Rust compilers?
-
Stop Comparing Rust to Old C++
There are three. The official one, mrustc (no borrow checker, but can essentially compile the official rustc) and GCC (can't really compile anything substantial yet). Only rustc is production-ready though.
-
Can I make it so that only the newest version of Rust gets installed?
That probably depends on what you mean by problematic. Having an ever increasing chain of dependencies isn’t the most desirable situation so there has been some work to trim the bootstrap chain. In 2018, when the blogpost I linked above was written, mrustc was used to bootstrap rust 1.19.0; now mrustc can bootstrap rust 1.54.0 so the chain to recent versions is much shorter than if all those intervening versions back through 1.19.0 needed to be built. https://github.com/thepowersgang/mrustc
What are some alternatives?
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
gccrs - GCC Front-End for Rust
osxcross - Mac OS X cross toolchain for Linux, FreeBSD, OpenBSD and Android (Termux)
gccrs - GCC Front-End for Rust
live-bootstrap - Use of a Linux initramfs to fully automate the bootstrapping process
llvm-cbe - resurrected LLVM "C Backend", with improvements
MacOSX-SDKs - A collection of those pesky SDK folders: MacOSX10.1.5.sdk thru MacOSX11.3.sdk
rust-ttapi
badger - Keyboard firmware written from scratch using Nim
miri - An interpreter for Rust's mid-level intermediate representation
gcc-rust - a (WIP) Rust frontend for gcc / a gcc backend for rustc