Matthias Klose <d...@debian.org> writes: > Package: gnubg > Version: 1.05.000-6 > Severity: important > Tags: sid stretch > User: debian-...@lists.debian.org > Usertags: non-standard-compiler, gcc-4.9, gcc-4.9-legacy
> This package builds with a non standard compiler version; please check > if this package can be built with the default version of gcc/g++, or > with gcc-5/g++-5. > Please keep this report open until the package uses the default > compiler version (or gcc-5) for the package build. > If the package cannot be built anymore, please file a bug report for > ftp.debian.org, asking for the removal of the package. > The severity of this report is likely to be raised before the release, > so that the gcc-4.9 package can be removed for the release. Okay, I've switched back to the default version of GCC and have disabled all optimization in the package build. Note, though, that there seems to be a substantial compiler regression in GCC 5 in the optimizer that affects at least this package. When built with GCC 5 with any optimization enabled, gnubg goes into a 100% CPU loop before main. I might be missing something, but I don't see any way that could be a bug in gnubg, as opposed to a regression in the compiler. (This is bug #807756, which I filed as important and you lowered to normal.) -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
