From: "Dave Korn" <dave.korn@artimi.com>
To: "'Dennis Clarke'" <dclarke@blastwave.org>, <gcc@gcc.gnu.org>
Subject: RE: MPFR 2.3.1 Release Candidate
Date: Sat, 29 Dec 2007 20:14:00 -0000 [thread overview]
Message-ID: <076001c84a56$c9155340$2e08a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <32991.72.39.216.186.1198958833.squirrel@mail.blastwave.org>
On 29 December 2007 20:07, Dennis Clarke wrote:
>
> Do you have a testsuite ? Some battary of tests that can be thrown at the
> code to determine correct responses to various calculations, error
> conditions, underflows and rounding errors etc etc ?
There's a "make check" target in the tarball. I don't know how thorough it
is.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2007-12-29 20:10 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 [this message]
2007-12-29 22:01 ` Dennis Clarke
2007-12-29 23:03 ` Vincent Lefevre
2008-01-01 5:17 ` Vincent Lefevre
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='076001c84a56$c9155340$2e08a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=dclarke@blastwave.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).