A Guide to Undefined Behavior in C and C++

Re:A Guide to Undefined Behavior in C and C++ by LegionMammal978 on Thursday August 17, 2023 @06:36PM (#37169148)

> 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 compiler built with only the Cranelift backend is perfectly capable of building another compiler. LLVM hasn't been a necessary component of the Rust compiler for quite some time.

[0] https://github.com/bjorn3/rustc_codegen_cranelift

[1] https://github.com/rust-lang/rust/pull/77975

[ Parent | on HN ]

Re:A Guide to Undefined Behavior in C and C++ by merlincorey on Friday August 18, 2023 @03:04AM (#37172222)

So then why wasn't the initial response "Rust is self hostable"?

Perhaps there's something we're both missing here.

[ Parent | on HN ]

Re:A Guide to Undefined Behavior in C and C++ by dralley on Friday August 18, 2023 @08:24AM (#37174685)

I 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

[ Parent | on HN ]