From 1ec69a3af27f390e7739c450aceabbd2fdf45916 Mon Sep 17 00:00:00 2001 From: vlefevre Date: Mon, 7 Jan 2019 01:11:12 +0000 Subject: [tests/tstrtofr.c] Updated comment about GCC bug 86554: the MPFR build is still affected with the latest gcc-snapshot version (20190102-1) when using --with-gmp-build=... together with --enable-assert. git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@13365 280ebfd0-de03-0410-8827-d642c229c3f4 --- tests/tstrtofr.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'tests/tstrtofr.c') diff --git a/tests/tstrtofr.c b/tests/tstrtofr.c index 74d68641d..d53b231a2 100644 --- a/tests/tstrtofr.c +++ b/tests/tstrtofr.c @@ -911,8 +911,10 @@ check_overflow (void) "(about this test)\nWorkaround: disable code hoisting " "with -fno-code-hoisting in CFLAGS.\n"); /* Note: In Debian, this error is obtained with gcc-snapshot from - 20180908-1 to 20181127-1. Versions 20181209-1 to 20190102-1 are - still buggy, but the MPFR build seems no longer affected. */ + 20180908-1 to 20181127-1. With gcc-snapshot from 20181209-1 to + 20190102-1 (at least), the MPFR build no longer seems affected + in general, but using --with-gmp-build=... together with + --enable-assert still triggers this failure. */ #endif exit (1); } -- cgit v1.2.1