From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] emulated fp on arm
Date: Wed, 30 Jan 2013 10:35:56 +0000 [thread overview]
Message-ID: <36de4d46283ce3f7afeed7cf21c23271@hamnavoe.com> (raw)
In-Reply-To: <d1329b9babc534669c4b183f34394a01@kw.quanstro.net>
> ARM -1 + 1 = -0 cmp 0 fail; cmp -0 fail
> 1 + -1 = 0 cmp 0 ok; cmp -0 ok
I know floating point add isn't associative, but I thought it was at
least meant to be commutative. The bug may not be where you think.
> the fpi guts are independent of the emulation on top, aren't they?
More or less. There's the question of how many secret extra bits
of precision to maintain internally, beyond the ones you get when
you store from a register.
next prev parent reply other threads:[~2013-01-30 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 17:08 erik quanstrom
2013-01-28 17:10 ` erik quanstrom
2013-01-29 22:10 ` Richard Miller
2013-01-29 22:44 ` erik quanstrom
2013-01-30 10:35 ` Richard Miller [this message]
2013-01-30 22:18 ` Bakul Shah
2013-01-31 3:50 ` erik quanstrom
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=36de4d46283ce3f7afeed7cf21c23271@hamnavoe.com \
--to=9fans@hamnavoe.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).