From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Martin Sebor <msebor@gmail.com>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>,
"Marc Glisse <marc.glisse@inria.fr>; Jakub Jelinek
<jakub@redhat.com>; Jonathan Wakely" <jwakely@redhat.com>
Subject: Re: [RFC] Update gmp/mpfr/mpc minimum versions
Date: Thu, 22 Sep 2016 18:16:00 -0000 [thread overview]
Message-ID: <AM4PR0701MB2162892B4022480642F427D4E4C90@AM4PR0701MB2162.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1609221757450.19208@digraph.polyomino.org.uk>
On 09/22/16 20:00, Joseph Myers wrote:
> On Thu, 22 Sep 2016, Bernd Edlinger wrote:
>
>> There is no feasible way how to make all gmp/mpfr/mpc versions from
>> minimal to latest build for all targets and all possible
>> cross-configurations.
>>
>> I hope that we do not "recommend" these versions.
>>
>> They are only the minimum versions for pre-installed packages.
>
> And personally I think it would by now be reasonable to require MPFR 3.0
> or 3.1 as a minimum version should someone wish to make the various
> cleanups mentioned in the April discussion, so avoiding claiming to
> support configurations few developers will be testing. (MPFR 3.1 came out
> nearly five years ago - 3 Oct 2011.)
>
Yes, and we have workarounds for more than just convenience features
that are missing in MPFR 2.4.
I proposed to remove them in April but Richard was against it.
Bernd.
next prev parent reply other threads:[~2016-09-22 18:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 18:23 Bernd Edlinger
2016-04-26 18:29 ` Jakub Jelinek
2016-04-26 18:42 ` Bernd Edlinger
2016-04-26 18:39 ` Marc Glisse
2016-04-26 19:01 ` Richard Biener
2016-04-26 19:05 ` Bernd Edlinger
2016-04-26 19:29 ` Marc Glisse
2016-04-27 14:01 ` Bernd Edlinger
2016-04-26 20:15 ` Joseph Myers
2016-04-27 15:31 ` Bernd Edlinger
2016-04-27 15:37 ` Rainer Orth
2016-04-27 15:47 ` Bernd Edlinger
2016-04-29 8:53 ` Rainer Orth
2016-09-22 17:32 ` Martin Sebor
2016-09-22 17:45 ` Joseph Myers
2016-09-22 17:55 ` Bernd Edlinger
2016-09-22 18:07 ` Joseph Myers
2016-09-22 18:10 ` Richard Biener
2016-09-22 18:16 ` Bernd Edlinger [this message]
2016-04-28 7:09 ` Richard Biener
[not found] ` <AM4PR07MB157126273516C6B5E78F4052E4650@AM4PR07MB1571.eurprd07.prod.outlook.com>
2016-04-28 12:35 ` [PATCH] Update gmp/mpfr/mpc in-tree versions Richard Biener
2016-04-28 14:22 ` Bernd Edlinger
2016-04-28 14:30 ` Richard Biener
2016-04-28 16:25 ` Bernd Edlinger
2016-04-29 7:46 ` Richard Biener
2016-04-29 13:26 ` Bernd Edlinger
2016-05-02 6:50 ` Richard Biener
2016-05-03 20:05 ` [RFC] Update gmp/mpfr/mpc minimum versions Bernd Edlinger
2016-05-04 7:46 ` Richard Biener
2016-09-22 18:13 Moritz Klammler
2016-09-22 18:21 ` Joseph Myers
2016-09-22 19:03 ` Bernd Edlinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM4PR0701MB2162892B4022480642F427D4E4C90@AM4PR0701MB2162.eurprd07.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=jwakely@redhat.com \
--cc=msebor@gmail.com \
--cc=rguenther@suse.de \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).