On 20.03.2016 20:12, Russ Allbery wrote:
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.

please could you recheck with GCC 6?

Reply via email to