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: Joseph Myers <joseph at codesourcery dot com>
- To: Bernd Edlinger <bernd dot edlinger at hotmail dot de>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, Richard Biener <rguenther at suse dot de>, Marc Glisse <marc dot glisse at inria dot fr>
- Date: Tue, 26 Apr 2016 20:14:44 +0000
- Subject: Re: [RFC] Update gmp/mpfr/mpc minimum versions
- Authentication-results: sourceware.org; auth=none
- References: <AM4PR07MB1571E7BDED31B7C146A0BC4CE4630 at AM4PR07MB1571 dot eurprd07 dot prod dot outlook dot com>
On Tue, 26 Apr 2016, Bernd Edlinger wrote:
> Hi,
>
> as we all know, it's high time now to adjust the minimum supported
> gmp/mpfr/mpc versions for gcc-7.
I think updating the minimum versions (when using previously built
libraries, not in-tree) is only appropriate when it allows some cleanup in
GCC, such as removing conditionals on whether a more recently added
function is available, adding functionality that depends on a newer
interface, or using newer interfaces instead of older ones that are now
deprecated.
For example, you could justify a move to requiring MPFR 3.0.0 or later
with cleanups to use MPFR_RND* instead of the older GMP_RND*, and
similarly mpfr_rnd_t instead of the older mp_rnd_t and likewise mpfr_exp_t
and mpfr_prec_t in fortran/. You could justify a move to requiring MPC
1.0.0 (or 1.0.2) by optimizing clog10 using mpc_log10. I don't know what
if any newer GMP interfaces would be beneficial in GCC. And as always in
such cases, it's a good idea to look at e.g. how widespread the newer
versions are in GNU/Linux distributions, which indicates how many people
might be affected by an increase in the version requirement.
--
Joseph S. Myers
joseph@codesourcery.com