From: Adrian Bunk <bunk@stusta.de>
To: Markus Milleder <markus.milleder@generali.at>
Cc: vincent+gcc@vinc17.org, fortran@gcc.gnu.org, gcc@gcc.gnu.org,
gcc-patches@gcc.gnu.org,
"Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Subject: Re: Antwort: Re: [PATCH]: bump minimum MPFR version, (includes some fortranbits)
Date: Mon, 13 Oct 2008 17:15:00 -0000 [thread overview]
Message-ID: <20081013154115.GH29938@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <OF07212AFF.43B9B068-ONC12574E1.004F00A3-C12574E1.0050C32A@AT.TOP.COM>
On Mon, Oct 13, 2008 at 04:42:08PM +0200, Markus Milleder wrote:
> Vincent Lefevre schrieb am 13.10.2008 16:16:38:
>
> > On 2008-10-07 21:42:30 +0300, Adrian Bunk wrote:
> > > But is there any "need to upgrade" to 2.3.2 since it would fix a bug
> > > gcc ran into?
> >
> > FYI, GCC can be affected by some bugs in MPFR 2.3.0, amongst the bugs
>
> <snip bug list>
>
> > All these bugs were fixed in MPFR 2.3.1. AFAIK, MPFR 2.3.2 should
> > not make any difference for GCC. The fixed bugs are listed here:
>
> <snip again>
>
> This seems to call for MPFR 2.3.1 as a minimum version for GCC 4.4
>
> However, let me ask the reverse question:
>
> Is there any reason not to demand 2.3.2 for GCC 4.4 ? Or even the newest MPFR version published before creating the GCC 4.4 release branch (which could be 2.3.3) ?
Upgrading can cause the user some unneeded work.
E.g. the next stable release of Debian will likely ship with 2.3.1 .
So in this specific case fulfilling a 2.3.1 requirement would be easy,
while a 2.3.2 requirement would make it much harder to build gcc 4.4 .
And upgrading from 2.3.1 to let's say 3.0.0 might be a bad choice if
the new version contains regressions.
> Markus Milleder
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-10-13 15:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 5:56 [PATCH]: bump minimum MPFR version, (includes some fortran bits) Kaveh R. GHAZI
2008-10-05 13:52 ` Richard Guenther
2008-10-05 14:10 ` Gerald Pfeifer
2008-10-05 14:43 ` Richard Guenther
2008-10-05 16:34 ` Manuel López-Ibáñez
2008-10-06 23:37 ` Kaveh R. Ghazi
2008-10-07 7:55 ` Janne Blomqvist
2008-10-06 13:56 ` Adrian Bunk
2008-10-06 23:16 ` [PATCH]: bump minimum MPFR version, (includes some fortranbits) Kaveh R. Ghazi
2008-10-06 23:40 ` Ben Elliston
2008-10-07 0:35 ` Andrew Pinski
2008-10-07 18:52 ` Adrian Bunk
2008-10-13 16:00 ` Vincent Lefevre
2008-10-13 16:42 ` Antwort: " Markus Milleder
2008-10-13 17:15 ` Adrian Bunk [this message]
2008-10-14 12:59 ` Antwort: " Markus Milleder
2008-10-14 13:10 ` Jakub Jelinek
2008-10-14 13:21 ` Tobias Schlüter
2008-10-14 14:52 ` Adrian Bunk
2008-10-14 15:39 ` Tobias Schlüter
2008-10-14 13:30 ` Antwort: Re: Antwort: " Adrian Bunk
2008-10-14 22:29 ` Nils Pipenbrinck
2008-10-14 22:31 ` Andrew Pinski
2008-10-15 0:59 ` Nils Pipenbrinck
2008-10-15 1:01 ` Andrew Pinski
2008-10-15 10:56 ` Brian Dessent
2008-10-15 1:09 ` Dave Korn
2008-10-26 12:59 ` [PATCH]: bump minimum MPFR version, (includes some fortran bits) Geoff Keating
2008-10-26 14:42 ` Jakub Jelinek
2008-10-27 2:50 ` Kaveh R. Ghazi
2008-10-27 7:03 ` David Edelsohn
2008-10-27 15:03 ` Joseph S. Myers
2008-10-27 15:14 ` Richard Guenther
2008-10-27 16:53 ` Joseph S. Myers
2008-10-27 20:34 ` Roberto Bagnara
2008-10-27 16:17 ` David Edelsohn
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=20081013154115.GH29938@cs181140183.pp.htv.fi \
--to=bunk@stusta.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
--cc=markus.milleder@generali.at \
--cc=vincent+gcc@vinc17.org \
/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).