3 ms·
> When this happens, it seems like it'll be possible to get the LLVM bits out of the bootstrap process and lead to a fully self-hosted Rust. What do you mean b
by LegionMammal978 3y ago
> When this happens, it seems like it'll be possible to get the LLVM bits out of the bootstrap process and lead to a fully self-hosted Rust.
What do you mean by "when this happens"? GP's point is that this has already happened: the Cranelift backend is feature-complete from the perspective of the language [0], except for inline assembly and unwinding on panic. It was merged into the upstream compiler in 2020 [1], and a Cranelift-based Rust compiler is perfectly capable of bootstrapping another Rust compiler (with some config changes) [2].
[0] https://github.com/bjorn3/rustc_codegen_cranelift https://github.com/bjorn3/rustc_codegen_cranelift
[1] https://github.com/rust-lang/rust/pull/77975 https://github.com/rust-lang/rust/pull/77975
[2] https://github.com/bjorn3/rustc_codegen_cranelift/actions/runs/5818852463/job/15776085253 https://github.com/bjorn3/rustc_codegen_cranelift/actions/ru...
- merlincorey 3y agoSo then why wasn't the initial response "Rust is self hostable"? Perhaps there's something we're both missing here.
- dralley 3y agoI mean, it kinda was. It was the last sentence in the first post. It wasn't my only response because 1) I couldn't remember if it had any significant limitations and couldn't be bothered to check 2) I still objected to the premise