gcc-10 was released yesterday and was pushed to ::gentoo's ~arch as:
Most of packages should Just Work. But we expect some amount of
build- and runtime breakage. Non-exhaustive list of things to watch for:
- missing includes in users' code
Example build failure would be:
"error: 'size_t' was not declared in this scope; did you mean 'std::size_t'?"
where missing <stdint.h> for used size_t types.
- extra '-fcommon->-fno-common' linker failures for packages that
ignore users' CFLAGS and thus missed Toralf's tinderbox runs.
- "9" -> "10" version change also managed to break many assumptions
of how gcc versions are parsed by shell scripts and ebuilds.
This causes all sorts of bizarre bugs:
- overhauled gcc-10 inliner heuristics will cause some amount of
build/runtime breakage in existing fragile code.
As an extreme example your stack-protected kernel might not boot:
Tracker of common breakages:
Landing page to steal-fixes-from/add-fixes-to:
If you can't figure out non-trivial breakage feel free to
add toolchain@ to the bug and we'll try to sort it out together.