CohenArthur

That's correct, the Rust-for-Linux project depends on the Rust core library, which is really essential to the language. As we wrote in the email, we still can't compile it fully or link against it. So Rust-for-Linux is still a future goal :)

We have `cargo-gccrs` for this, so a cargo subcommand which intercepts arguments given to `rustc` and converts them into `gccrs` arguments :)

https://github.com/rust-GCC/cargo-gccrs/

it's still in a relatively early stage as we are focusing on the compiler. But the idea is for it to be a drop-in replacement for compilation and execution operations, so you'd have `cargo gccrs build`, `cargo gccrs run`, `cargo gccrs test`, etc

It's important to note that mrustc is not intended for everyday use and instead as a bootstrap compiler for rustc (at least originally).

We would like to develop an alternative that is suitable as a daily rust compiler and that integrates into the existing Rust ecosystem (and makes use of it!)

This is a recording of a talk Philip and I gave during the Live Embedded Event. We didn't really plan on it being posted here :)

If you are interested in our work, we regularly publish reports (weekly and monthly which would be a better starting point and contain more fun info) on our GitHub organization and on thephilbert.io

Additionally, we wrote a blogpost on the compiler which should get released soon!

I wouldn't watch that video in my office either :D