9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrew zerger <rhoyerboat@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] circular fonctions: precision?
Date: Sun,  2 Oct 2011 12:59:36 -0600	[thread overview]
Message-ID: <CAEDadrxT2psD3AED-cgamujy-zR-_n-kxiCX050wAhU0UbfiKA@mail.gmail.com> (raw)
In-Reply-To: <1a3de3d2869ab078c9a4fdf9bce44982@brasstown.quanstro.net>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

 havent read any of these specs but im sitting here thinking that bits on a
processor that can subtract == more preicision ..

On Sun, Oct 2, 2011 at 12:44 PM, erik quanstrom <quanstro@quanstro.net>wrote:

> > IEEE754-1985 didn't specify circular, hyperbolic or other
> > advanced functions. You can have 754 compliant hardware and
> > not implement these functions. In any case the standard can
> > not dictate the accuracy of functions not specified in it. An
> > iterative algorithm may lose more than 1 bit of accuracy since
> > iterations won't be done in infinite precision. One can not
> > assume accuracy to a bit even where these functions are
> > imeplemented in h/w.  For x86, accuracy may be specified in
> > some Intel or AMD manual.
>
> that wasn't my reading of the spec.  so you're saying that if
> the iterative algorithm loops 53 times, it's free to return any
> answer whatever and still be compliant?
>
> - erik
>
>


-- 
⎼⎺⎺├@┼␊├├≤-␍⎼␊▒␍:/␤⎺└␊/⎼␤⎺#

[-- Attachment #2: Type: text/html, Size: 1444 bytes --]

  reply	other threads:[~2011-10-02 18:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-02 16:38 tlaronde
2011-10-02 17:52 ` Bakul Shah
2011-10-02 18:06   ` erik quanstrom
2011-10-02 18:40     ` Bakul Shah
2011-10-02 18:44       ` erik quanstrom
2011-10-02 18:59         ` andrew zerger [this message]
2011-10-02 19:04         ` tlaronde
2011-10-02 19:14         ` Bakul Shah
2011-10-02 19:18           ` erik quanstrom
2011-10-02 18:44     ` tlaronde
2011-10-02 18:48       ` tlaronde
2011-10-02 18:28   ` tlaronde
2011-10-02 19:06     ` Bakul Shah
2011-10-03 11:41       ` tlaronde
2011-10-03 14:39         ` Bakul Shah
2011-10-03 14:46           ` erik quanstrom
2011-10-03 15:29             ` Bakul Shah
2011-10-03 15:58               ` Bakul Shah
2011-10-03 16:49           ` tlaronde
2011-10-03 13:03 ` Russ Cox
2011-10-03 14:44   ` Bakul Shah
2011-10-03 14:57     ` Russ Cox
2011-10-03 15:34       ` Bakul Shah
2011-10-03 15:47         ` Russ Cox
2011-10-03 16:53   ` tlaronde

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=CAEDadrxT2psD3AED-cgamujy-zR-_n-kxiCX050wAhU0UbfiKA@mail.gmail.com \
    --to=rhoyerboat@gmail.com \
    --cc=9fans@9fans.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 NNTP newsgroup(s).