Re: [PATCH] work around MPFR undefined behavior (PR 78786)

2016-12-14 Thread Martin Sebor
On 12/14/2016 02:25 AM, Andreas Schwab wrote: On Dez 14 2016, Martin Sebor wrote: +#define target_dir_max() (target_int_max () + 4932 + 2) + if (9864 < prec) + prec = 9864; Should these two magic numbers be macroized? I had considered it and didn't think it was worth it (th

Re: [PATCH] work around MPFR undefined behavior (PR 78786)

2016-12-14 Thread Andreas Schwab
On Dez 14 2016, Martin Sebor wrote: > +#define target_dir_max() (target_int_max () + 4932 + 2) > + if (9864 < prec) > + prec = 9864; Should these two magic numbers be macroized? Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1

Re: [PATCH] work around MPFR undefined behavior (PR 78786)

2016-12-13 Thread Jeff Law
On 12/13/2016 09:07 PM, Martin Sebor wrote: In a discussion of my patch for bug 78696 I mentioned I had found a bug/limitation in MPFR that causes GCC to allocate excessive amounts of memory on some corner cases (very large precision). https://gcc.gnu.org/ml/gcc-patches/2016-12/msg01098.html

[PATCH] work around MPFR undefined behavior (PR 78786)

2016-12-13 Thread Martin Sebor
In a discussion of my patch for bug 78696 I mentioned I had found a bug/limitation in MPFR that causes GCC to allocate excessive amounts of memory on some corner cases (very large precision). https://gcc.gnu.org/ml/gcc-patches/2016-12/msg01098.html I've since raised GCC bug 78786 for the GCC p