Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 4 Dec 2005 23:19:23 -0600 (CST)
From:      Mike Silbersack <silby@silby.com>
To:        Bruce Evans <bde@zeta.org.au>
Cc:        src-committers@freebsd.org, Andre Oppermann <andre@freebsd.org>, cvs-src@freebsd.org, cvs-all@freebsd.org, Bruce Evans <bde@freebsd.org>, Steve Kargl <sgk@troutmask.apl.washington.edu>, Andrey Chernov <ache@freebsd.org>
Subject:   Re: cvs commit: src/lib/msun/src e_lgammaf_r.c
Message-ID:  <20051204231731.N43418@odysseus.silby.com>
In-Reply-To: <20051129184901.I34802@delplex.bde.org>
References:  <200511280832.jAS8WGvs059057@repoman.freebsd.org> <438AD8FB.A8B96AB6@freebsd.org> <20051128172718.GA59929@troutmask.apl.washington.edu> <20051129110058.T33820@delplex.bde.org> <20051129012102.GA84108@nagual.pp.ru> <20051129184901.I34802@delplex.bde.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On Tue, 29 Nov 2005, Bruce Evans wrote:

> On Tue, 29 Nov 2005, Andrey Chernov wrote:
>
>> On Tue, Nov 29, 2005 at 11:49:13AM +1100, Bruce Evans wrote:
>>> I don't like writing papers, and rarely read them these days.
>> 
>> Not writting the paper about your libm changes will increase chances your
>> changes will be simple lost at some step. Possible scenario: 1) One of
>
> They won't be lost, becaue they are in cvs :-).

Would it be possible to write regression tests which verify that accuracy 
is not lost due to future changes to libm?  That would be the best way to 
ensure that your work is not lost in the future.

Mike "Silby" Silbersack



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051204231731.N43418>