From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5660 invoked by alias); 9 Dec 2007 23:21:35 -0000 Received: (qmail 5650 invoked by uid 22791); 9 Dec 2007 23:21:33 -0000 X-Spam-Check-By: sourceware.org Received: from py-out-1112.google.com (HELO py-out-1112.google.com) (64.233.166.176) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 09 Dec 2007 23:21:27 +0000 Received: by py-out-1112.google.com with SMTP id a29so4307882pyi for ; Sun, 09 Dec 2007 15:21:23 -0800 (PST) Received: by 10.64.91.15 with SMTP id o15mr12497561qbb.1197242482024; Sun, 09 Dec 2007 15:21:22 -0800 (PST) Received: by 10.64.91.5 with HTTP; Sun, 9 Dec 2007 15:21:21 -0800 (PST) Message-ID: <84fc9c000712091521w11b4ef73i4418cb873496a579@mail.gmail.com> Date: Mon, 10 Dec 2007 00:37:00 -0000 From: "Richard Guenther" To: "Kaveh R. GHAZI" Subject: Re: Revisiting GCC's minimum MPFR version Cc: gcc@gcc.gnu.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2007-12/txt/msg00300.txt.bz2 On Dec 9, 2007 11:05 PM, Kaveh R. GHAZI wrote: > As requested by Richard G here: > http://gcc.gnu.org/ml/gcc-patches/2007-05/msg00945.html > > I'm re-visiting during stage3 the minimum MPFR version required by GCC. > At the time of the above post, mpfr-2.3.0 had not yet been released, but > it was this past August, and one can obtain it here: > http://www.mpfr.org/mpfr-current > > The current situation is that GCC requires only mpfr-2.2.0, however it > recommends mpfr-2.2.1 in the documentation and configure checks. (If > configure find 2.2.0, it will say something like "buggy but acceptable" > and continue bootstrapping). > > Also, there is some functionality for builtin bessel, remquo and gamma > functions that is only active when mpfr-2.3.0 is available. The testcase > gcc.dg/torture/builtin-math-4.c for these mpfr-2.3.0 functions is XFAILed > at the moment. > > > Our options include: > > 1. Do nothing. Things work, don't break it. Revisit again in stage1. > > 2. Continue accepting 2.2.0, but update the recommended version from > 2.2.1 to 2.3.0. This would entail updating the configure warning, > the docs and the removing the XFAIL from the testcase. This > option would cause no change in hard bootstrap requirements. > > 3. In addtion to #2, hard fail for anything less than mpfr-2.3.0. > > > I have no strong opinion on which way to go. I would update the recommended version to 2.3.0 and fail for anything less than 2.2.1. Richard.