From: Rich Felker <dalias@aerifal.cx>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: libc-ports@sourceware.org, libc-alpha@sourceware.org,
Doug Gilmore <Doug.Gilmore@imgtec.com>
Subject: Re: [RFC][PATCH] MIPS: IEEE 754-2008 NaN encoding support
Date: Fri, 23 Aug 2013 03:46:00 -0000 [thread overview]
Message-ID: <20130823034617.GP20515@brightrain.aerifal.cx> (raw)
In-Reply-To: <alpine.DEB.1.10.1308222343480.8514@tp.orcam.me.uk>
On Fri, Aug 23, 2013 at 12:52:43AM +0100, Maciej W. Rozycki wrote:
> As from revision 3.50 [2][3] the MIPS Architecture provides for
> processors that support the IEEE 754-2008 preferred NaN encoding format.
> As the two formats (further referred to as "legacy NaN" and "2008 NaN")
> are incompatible to each other, tools will have to provide support for the
> two formats to help people avoid using incompatible binary modules. Here
> is the glibc part.
> [...]
> References:
>
> [1] "IEEE Standard for Floating-Point Arithmetic", IEEE Computer Society,
> IEEE Std 754-2008, 29 August 2008
>
> [2] "MIPS Architecture For Programmers, Volume I-A: Introduction to the
> MIPS32 Architecture", MIPS Technologies, Inc., Document Number:
> MD00082, Revision 3.50, September 20, 2012
>
> [3] "MIPS Architecture For Programmers, Volume I-A: Introduction to the
> MIPS64 Architecture", MIPS Technologies, Inc., Document Number:
> MD00083, Revision 3.50, September 20, 2012
These documents do not seem to be publicly available; I can only mind
much older versions online, such as 0.95:
http://www.ece.lsu.edu/ee4720/mips64v1.pdf
Perhaps you could quote some of the relevant text?
Rich
next prev parent reply other threads:[~2013-08-23 3:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 23:53 Maciej W. Rozycki
2013-08-23 0:58 ` Rich Felker
2013-08-23 1:41 ` Maciej W. Rozycki
2013-08-23 1:57 ` Rich Felker
2013-08-23 3:11 ` pinskia
2013-08-23 3:38 ` Rich Felker
2013-08-23 4:08 ` pinskia
2013-08-23 4:12 ` Rich Felker
2013-08-23 4:10 ` Rich Felker
2013-08-23 3:46 ` Rich Felker [this message]
2013-08-23 10:53 ` Maciej W. Rozycki
2013-08-23 15:26 ` Joseph S. Myers
2013-09-05 22:47 ` [RFC][PATCH v2] " Maciej W. Rozycki
2013-09-06 16:24 ` Joseph S. Myers
2013-09-10 9:36 ` Maciej W. Rozycki
2013-09-10 23:24 ` Joseph S. Myers
2013-09-16 15:14 ` [PATCH v3] " Maciej W. Rozycki
2013-09-16 15:26 ` Joseph S. Myers
2013-09-18 20:48 ` Maciej W. Rozycki
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=20130823034617.GP20515@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=Doug.Gilmore@imgtec.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=macro@codesourcery.com \
/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).