Considering that Ferrocene has been open sourced (or at least, will be) and Adacore announced the (seemingly) closed source GNAT Pro for Rust, it looks to me that maybe the two organizations couldn't agree on a path forward regarding source availability and parted ways. Even this post mentions that the current version of Ferrocene needs to have some "proprietary partner work" scrubbed before a proper open source release can occur.
Ken Thompson talked about compilers potentially injecting code in final programs in his Turing Award lecture [1]. That's why compilers need to be certified in order for the software built by these compilers also receive certification.<p>It's a great step for Rust!<p>[1]: <a href="https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf" rel="nofollow noreferrer">https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_Ref...</a>
Hopefully the work on Ferrocene can contribute to the standardization of the Rust language.<p>Tracking issue: <a href="https://github.com/rust-lang/rust/issues/113527">https://github.com/rust-lang/rust/issues/113527</a>
This is really cool. A really big step forward for the Rust ecosystem. Being able to use Rust in safety critical systems is a big win.<p>Congrats to everyone involved!
Kudos to the team! I'm almost sad that I'm not working anymore on a Battery Management System, requiring functional safety, as I was considering transitioning from C to Rust and that's how I came to learn about Ferrocene :)
Interesting that they only support x86-64 and aarch64/ARM64.<p>I would have thought the majority of safety critical systems are on bare-metal ARM32.