Syncing Rust GCC backend or how to test Murphy's law
Summary
This article chronicles the process of syncing the Rust GCC backend across two repositories using git subtree, detailing the workflow, multiple issues encountered (license, CI mirroring, caching, GCC changes, binutils, miri) and the eventual completion. It highlights the challenges of cross repo code generation in large open source projects.