--- Оригінальне повідомлення ---
Від кого: "Marco Bodrato"
Дата: 16 травня 2018, 09:41:23
> Tested, and pushed.
>
> https://gmplib.org/repo/gmp/rev/9da2c35e811c
It works fine. Thanks to all involved!
But shouldn't GMP testsuite be updated too, as Paul Zimmermann suggested:
https://gmplib.
Ciao,
Il Gio, 18 Gennaio 2018 4:07 pm, Vincent Lefevre ha scritto:
> On 2018-01-18 14:16:41 +0100, Vincent Lefevre wrote:
>> printf/repl-vsnprintf.c seems buggy for floating-point specifiers
>> (EeGgFf). Replace "break" by "goto next" (2 occurrences)?
>
> Proposed patch attached. Not tested.
Test
-Original Message-
From: Vincent Lefevre
Sent: Friday, January 19, 2018 1:07 AM
To: sisyph...@optusnet.com.au ; paul zimmermann ; sav...@ukr.net ;
gmp-bugs@gmplib.org
Subject: Re: printf/repl-vsnprintf.c bug (was: GMP|MPIR|MPFR assertions)
printf/repl-vsnprintf.c seems buggy for
--- Оригінальне повідомлення ---
Від кого: "Vincent Lefevre"
Дата: 18 січня 2018, 16:07:10
> Proposed patch attached. Not tested.
--- Оригінальне повідомлення ---
Від кого: "paul zimmermann"
Дата: 18 січня 2018, 16:16:44
> here is a test case to reproduce the issue (you have to test it
it should be noted that this bug was not found by GMP's "make check"
(to my best knowledge), but only by MPFR's test suite.
Before fixing the bug, it would be nice to fix the GMP test suite.
Paul
___
gmp-bugs mailing list
gmp-bugs@gmplib.org
https://gm
> > printf/repl-vsnprintf.c seems buggy for floating-point specifiers
> > (EeGgFf). Replace "break" by "goto next" (2 occurrences)?
>
> Proposed patch attached. Not tested.
here is a test case to reproduce the issue (you have to test it on a system that
doesn't have vsnprintf, or only has a broke
On 2018-01-18 14:16:41 +0100, Vincent Lefevre wrote:
> [Cc to gmp-bugs]
>
> On 2018-01-18 23:14:12 +1100, sisyph...@optusnet.com.au wrote:
> > Just had a reply on the mingw64 mailing list.
> > Apparently, the test programs are not crashing - abort() is being called
> > following an assertion failu
[Cc to gmp-bugs]
On 2018-01-18 23:14:12 +1100, sisyph...@optusnet.com.au wrote:
> Just had a reply on the mingw64 mailing list.
> Apparently, the test programs are not crashing - abort() is being called
> following an assertion failure.
> And this calls for a "break abort" prior to "run" being cal
