=sys-devel/gcc-9.2.0-r1 stabilization bug. Not CC-ing arches just yet as I'd like to give a heads up to wider audience first.
Sent out a -del ML announcement as: https://archives.gentoo.org/gentoo-dev/message/c1ec6010b1b36d60b59e891cd2a77d94
Arches, please stabilize =sys-devel/gcc-9.2.0-r2 for KEYWORDS alpha amd64 arm arm64 hppa ia64 m68k ppc ppc64 s390 sh sparc x86 Many tests are known broken and should be ignored or looked at individually.
arm64 stable
amd64 stable
x86 stable
s390 stable
sparc stable
ppc64 stable
alpha stable
ppc stable
ia64 stable
hppa stable
arm stable
Before this is stabilized, this commit needs to be backported https://github.com/gcc-mirror/gcc/commit/3d9bf16ac2ce6643e4240cdd0c65f7aabc4aae61 either several packages will fail to build/work properly (like llvm) with the error: "The futex facility returned an unexpected error code."
(In reply to David Carlos Manuelda from comment #16) > Before this is stabilized, this commit needs to be backported > https://github.com/gcc-mirror/gcc/commit/ > 3d9bf16ac2ce6643e4240cdd0c65f7aabc4aae61 either several packages will fail > to build/work properly (like llvm) with the error: > > "The futex facility returned an unexpected error code." Please file a separate bug. gcc-9.2.0 stabilization is already done for most arches.
SuperH port disbanded.
m68k dropped stable keywords Last arch. Closing.