This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Update gmp/mpfr/mpc minimum versions
- From: Bernd Edlinger <bernd dot edlinger at hotmail dot de>
- To: Marc Glisse <marc dot glisse at inria dot fr>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, Richard Biener <rguenther at suse dot de>
- Date: Tue, 26 Apr 2016 19:05:02 +0000
- Subject: Re: [RFC] Update gmp/mpfr/mpc minimum versions
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=softfail (sender IP is 25.152.4.51) smtp.mailfrom=hotmail.de; inria.fr; dkim=none (message not signed) header.d=none;inria.fr; dmarc=none action=none header.from=hotmail.de;
- References: <AM4PR07MB1571E7BDED31B7C146A0BC4CE4630 at AM4PR07MB1571 dot eurprd07 dot prod dot outlook dot com> <alpine dot DEB dot 2 dot 20 dot 1604262029310 dot 2084 at laptop-mg dot saclay dot inria dot fr>
On 26.04.2016 20:39, Marc Glisse wrote:
> On Tue, 26 Apr 2016, Bernd Edlinger wrote:
>
>> as we all know, it's high time now to adjust the minimum supported
>> gmp/mpfr/mpc versions for gcc-7.
>>
>> So this attached patch is now targeting at only supporting the currently
>> latest relased gmp-6.1.0, mpfr-3.1.4 and mpc-1.0.3, instead of trying
>> to support all previous versions, especially in-tree, but also without
>> the
>> in-tree configuration the previously used versions are really creating
>> trouble nowadays.
>
> For in-tree builds, requiring the latest version makes sense to me. When
> building gcc with a pre-installed gmp/mpfr/mpc (say the one provided by
> your linux distribution), that's much more painful, and the benefit is
> not as clear. What "trouble" do you have in mind?
>
For instance PR libstdc++/69881: gmp.h did this:
#define __need_size_t /* tell gcc stddef.h we only want size_t */
#include <cstddef> /* for size_t */
I've persuaded Jonathan to work around that in libstdc++.
Of course the in-tree build does work with less versions than
otherwise.
>> To support gmp-6.1.0 in-tree we have to set AM_CFLAGS=-DNO_ASM
>> as already done with mpfr. This was already discussed recently on
>> this list.
>
> Note that gmp-6.1.1 is supposed to be out any day now and will not
> require -DNO_ASM anymore.
>
Yes, I know. I mean, I have tested the patch already with the gmp
snapshots, but was not aware that it will be available so soon.
However I think it would not really hurt to allow a little
more interoperability, even for in-tree builds.
It is just a matter what versions we want to test, I have not really
any idea where the limits will be, just that it can no longer be 4.3.2.
Thanks
Bernd.