News for hackers. Stuff that matters.
Re:Resigning as Asahi Linux project lead by kibwen on Thursday February 13, 2025 @01:53PM (#43039709)
Not even close to 100%, the reason that it feels like every major C codebase in industry is pinned to some ancient compiler version is because upgrading to a new toolchain is fraught. The fact that most Rust users are successfully tracking relatively recent versions of the toolchain is a testament to how stable Rust actually is in practice (an upgrade might take you a few minutes per million lines of code).
Re:Resigning as Asahi Linux project lead by umanwizard on Thursday February 13, 2025 @09:02PM (#43043891)
IDK about "industry" but I can't think of any prominent C or C++ open-source codebase that requires a specific version of gcc or clang to compile.
Re:Resigning as Asahi Linux project lead by dralley on Thursday February 13, 2025 @09:46PM (#43044201)
The Linux kernel was that way for a while, years ago.
Re:Resigning as Asahi Linux project lead by dezgeg on Friday February 14, 2025 @03:24AM (#43046138)
Try following your favourite distro's bug tracker during GCC upgrade. Practically every update breaks some packages, sometimes less, sometimes more (esp. when GCC changes their default flags).

Here's one example of workarounds in ~100 packages that broke when upgrading to GCC 10: https://github.com/search?q=repo%3ANixOS%2Fnixpkgs%20fcommon...