On Nov 20, 2024 at 22:22 +0800, Ken Cunningham <[email protected]>, wrote: > Any concrete example of something gcc-14 breaks that gcc-13 builds?
A lot in fact, but for a reason orthogonal to toolchain as such. gcc14 became stricter with warnings vs errors, so either all affected ports’ code has to be fixed (in practice this usually translates into “fixed by who builds those with gcc”, i.e. typically myself), which requires hours and hours, or folks with “veto rights” should not prevent at least fixing these ports by adding a `-Wno-error=` flag (which is done in numerous ports for clangs, but for gcc it every time turns into an argument). Other than that no, I believe, and neither gcc7 can build something which gcc14 cannot (and which is actually needed).
