Hi everyone,
Regarding blockers against bug #461954 "(gcc-4.8) GCC 4.8 porting" and
bug #516152 "(gcc-4.8-stable) sys-devel/gcc-4.8.? stabilization" here is
the current situation:
bug #516548 - (PR61538) broken atomic on MIPS R10000
-> As far as I can tell, this only effects R10000. It does not effect
the fulong or longson (lemote netbooks), nor some other router boards i
have.
bug #503838 - (PR60465) sys-libs/glibc: building w/gcc-4.8 crashes early
on ia64
-> This effects only ia64.
bug #500064 - app-emulation/virtualbox-4.3.6 fails to build with gcc
4.8.x in bundled iPXE
-> Poly-C wants to stabilize these along side gcc-4.8.
bug #465268 - dev-embedded/msp430-gcc-4.6.3_p20120406 with gcc-4.8.0
-> This is working with gcc-4.9 and doesn't need to hold up 4.8.
bug 458706 - PaX: Max. per-task virtual memory too small for llvm asan
and gcc-4.8 asan
-> AddressSanitizer doesn't work with a PaX hardened kernel. Nor does it
work on several arches nor on musl. vapier has done some masking here.
bug 513386 - net-libs/webkit-gtk-2.4.3 - ./.libs/libwebkitgtk-3.0.so:
undefined reference to `_ZNSt6chrono12steady_clock3nowEv@GLIBCXX_3.4.17'
-> This is a problem. It relates to abi mismatching with libstdc++.
The bug details how you can hit it in gentoo. Martin von Gagern pushed
the issue upstream and pretty much got the answer "we're on our own" So
we'll have to deal with this as we go forward.
Seehttps://gcc.gnu.org/bugzilla/show_bug.cgi?id=61758
So except for some minor arch issue and bug 513386, which we're going to
have to deal with for a while, gcc-4.8.3 looks good. I went ahead and
stabilized it on ppc and ppc64. Its also stable on arm and hppa. I
don't want to speak for any other arch teams, but it may be time.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : bluen...@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
