CohenArthur

3 ms·

1. 1.▲
   gccrs February 2025 Monthly report(rust-gcc.github.io)

   4 points by CohenArthur 2y ago|0 comments
2. 2.▲
   (Re)using rustc components in gccrs(rust-gcc.github.io)

   3 points by CohenArthur 2y ago|0 comments
3. 3.▲
   Gccrs August 2024 monthly report(rust-gcc.github.io)

   2 points by CohenArthur 2y ago|0 comments
4. 4.▲
   by CohenArthur 4y ago

   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 fut
5. 5.▲
   by CohenArthur 4y ago

   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 relativel
6. 6.▲
   by CohenArthur 4y ago

   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 integra
7. 7.▲
   by CohenArthur 4y ago

   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 bette