public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stephen L Moshier <steve@moshier.net>
To: Andrew Haley <aph@redhat.com>
Cc: Robert Dewar <dewar@gnat.com>, <gdr@integrable-solutions.net>,
	<gcc@gcc.gnu.org>
Subject: Re: real.c fails floating point tests
Date: Wed, 16 Oct 2002 11:30:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0210161230180.21308-100000@moshier.net> (raw)
In-Reply-To: <15789.33220.275613.708118@cuddles.cambridge.redhat.com>


On Wed, 16 Oct 2002, Andrew Haley wrote:

> Robert Dewar writes:
>  >
>  > Stephen, how easy would it be to install the paranoia test in an easily
>  > reusable form, so that this test can be run periodically?
>
> It's already been done, in contrib/paranoia.cc.

By way of warning, this does not seem entirely as advertised.
contrib/paranoia.cc is not testing the internal real.c arithmetic.
Also it is otherwise incomplete as it stands.  For example, it is
using the host computer's math library for the log, exp, pow
functions.  That defeats many of the paranoia tests.  The reported
abort was in pow2test, involving an arithmetic bug stimulated by the
pow function written in real.c's arithmetic.  So paranoia.cc is a
weakened test; it needs some more work to finish it, and it should
also test the internal arithmetic (the functions now called do_add,
do_divide, etc. in real.c).

I used to keep a functional test harness for real.c and various tests
for it (including paranoia and a C++ class to overload arithmetic
calls) but lost track when the gcc development moved to Cygnus.
Adapting and updating for the many gcc changes since then is not
something I have free time for at present.  The decimal to binary
conversion is the only item there that I need as a user, in self
defense, to have working, and what little time I do have for this now
is concentrated on that.

Sorry, but I do not have time either to get into a flame war.
I am not a software prima donna, I am just an irate customer.

  reply	other threads:[~2002-10-16 17:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16  9:58 Robert Dewar
2002-10-16 10:12 ` David Edelsohn
2002-10-16 10:16 ` Andrew Haley
2002-10-16 11:30   ` Stephen L Moshier [this message]
2002-10-16 10:23 ` Gabriel Dos Reis
2002-10-16 11:54 ` Mark Mitchell
2002-10-16 15:54   ` Richard Henderson
2002-10-16 16:31     ` Mark Mitchell
  -- strict thread matches above, loose matches on Subject: below --
2002-10-18  9:11 Robert Dewar
2002-10-17  8:55 Joern Rennecke
2002-10-17 13:44 ` Richard Henderson
2002-10-17  6:00 Robert Dewar
2002-10-17  5:22 Robert Dewar
2002-10-16  9:28 Robert Dewar
2002-10-16  8:19 Stephen L Moshier
2002-10-16  9:47 ` Gabriel Dos Reis
2002-10-16 14:54 ` Richard Henderson
2002-10-16 15:29   ` Stephen L Moshier
2002-10-16 15:36     ` Richard Henderson
2002-10-16 17:20       ` Stephen L Moshier
2002-10-16 21:16         ` Richard Henderson
2002-10-18  7:32           ` Stephen L Moshier

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=Pine.LNX.4.44.0210161230180.21308-100000@moshier.net \
    --to=steve@moshier.net \
    --cc=aph@redhat.com \
    --cc=dewar@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    /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).