public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vincent Lefevre <vincent+gcc@vinc17.org>
To: gcc@gcc.gnu.org
Subject: Re: MPFR 2.3.1 Release Candidate
Date: Tue, 01 Jan 2008 05:17:00 -0000	[thread overview]
Message-ID: <20080101051701.GG6543@ay.vinc17.org> (raw)
In-Reply-To: <20071229222539.GA4660@ay.vinc17.org>

On 2007-12-29 23:25:39 +0100, Vincent Lefevre wrote:
>   * Some functions were failing when some global flag was set before
>     the call, and unfortunately most tests were done with all flags
>     cleared. Now, in the generic tests, all the global flags are
>     set before a test with a probability 1/2 (part of r5115).

Unfortunately, there was a bug in these tests, with the consequence
that the value wasn't checked (so, these tests could only detect
assertion failures or freeze). I've just fixed it and another bug
in reciprocal trig/hyperbolic functions which wasn't detected because
of that. If GCC calls these functions with all the flags cleared, it
isn't affected by this bug.

Moreover there is now an mpfrlint script (available via Subversion)
that can be used to detect bad constructs; it should have detected
the above bug, but was incomplete. Again, fixed.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

  reply	other threads:[~2008-01-01  5:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-29 20:07 Vincent Lefevre
2007-12-29 20:10 ` Dennis Clarke
2007-12-29 20:14   ` Dave Korn
2007-12-29 22:01     ` Dennis Clarke
2007-12-29 23:03     ` Vincent Lefevre
2008-01-01  5:17       ` Vincent Lefevre [this message]
2007-12-31 22:44 ` Kaveh R. GHAZI
2008-01-01  5:08   ` Vincent Lefevre
2008-01-02  6:07     ` Kaveh R. GHAZI
2008-01-02 12:13       ` Vincent Lefevre
2008-01-04  2:54         ` Kaveh R. GHAZI
2008-01-04  8:06           ` Vincent Lefevre

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=20080101051701.GG6543@ay.vinc17.org \
    --to=vincent+gcc@vinc17.org \
    --cc=gcc@gcc.gnu.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).