GCC Rust

Here is our report for the first month of 2026, with an interesting little dive into a name resolution problem we fixed this month :) rust-gcc.github.io/2026/02/10/202…

Hi everyone! Here is our last report for the year 2025 and a small update from the team. Thanks again for a very fun 2025 and we look forward to do it all over again :) rust-gcc.github.io/2026/01/08/202…

rust-gcc.github.io/2025/09/09/202… Short report for the month of August and a recap of the work done this summer - we're full steam ahead working on compiling core and the kernel's crate!

Monthly report for July 2025: rust-gcc.github.io/2025/08/05/202…

Our report for the month of June: rust-gcc.github.io/2025/07/17/202… Still making good progress and progressing fast towards testing the kernel's alloc crate

New report for the month of May: rust-gcc.github.io/2025/06/04/202… We are making good progress on core and plan on begin testing the Rust code in the kernel at the end of the summer!

Monthly report for the month of March: rust-gcc.github.io/2025/04/15/202… Which mentions some of the work done for supporting specialization in `core` :) We've upstreamed 600 commits to GCC this month and will continue to do so until 15.1 releases!

Here is our monthly report for February, with more explanations of the features we are currently working on. See you all in Paris tomorrow for Rust In Paris 2025! rust-gcc.github.io/2025/03/10/202…

First monthly report of the year with some code snippets of our two main targets (Rust-for-Linux and Rust's core crate) to show the importance of the milestones we are working on: rust-gcc.github.io/2025/02/06/202…

Here is our monthly report for the month of December 2024, which includes a small technical dive into the handling of auto traits and the desugaring of for-loops: rust-gcc.github.io/2025/01/07/202…

New monthly report for November is out, with a slight dive into type-system fun :) and most importantly contributions from the rustc_codegen_gcc folks! rust-gcc.github.io/2024/12/02/202…

We have written a short technical dive into how we currently reuse Rust components within gccrs, a compiler written in C++, and how we will continue doing so in the future, eventually compiling them using our own compiler. rust-gcc.github.io/2024/09/20/reu…

After 7 years, there will finally be another "Rust All Hands" event where all members of the Rust project come together in person to collaborate on the future of Rust. 🎉 The All Hands will be part of @Rust_NL's "Rust Week 2025" in Utrecht, Netherlands. blog.rust-lang.org/inside-rust/20…

We have also uploaded our engineering document for the upcoming years of work: rust-gcc.github.io/2024/09/03/tow… This outlines future milestones we will be tackling. The goal is to help us picture when gccrs will start being useful for projects such as Rust-for-Linux or embedded software.

As a reminder, here are their Github profiles: please follow them and sponsor them if you can ❤️ github.com/badumbatish/ (@thisisjjasmine) github.com/braw-lee/ (@bald_chimaev) github.com/MahadMuhammad/ (@_mmahad)

The monthly report for August 2024 is out: rust-gcc.github.io/2024/09/03/202… GSoC is now over, with amazing work from our three students @thisisjjasmine, @bald_chimaev and @_mmahad. They all want to continue working on the project in their free time, which makes us super happy ❤️

As a reminder, gccrs uses the polonius-engine Rust crate to do its borrow-checking. This is an old version of the polonius borrow-checker, and not the one being currently developed, but we follow the work closely and aim to help integrate it and crate-ify it as soon as possible!

Of course, we are still nowhere close to how good and helpful rustc's errors are. If anyone is interested in adding helpful hints to our borrow checker errors, please get in touch! This is not critical at the moment, but this is something we'd love to work on

GSoC is over, and thanks to our wonderful students we now have a lot more features and tooling which will help the compiler in the long run. One of those user-facing features is the proper handling of borrow-checker errors, which now have helpful error messages and proper locus!