From: Joseph Myers <joseph@codesourcery.com>
To: Andrew Waterman <andrew@sifive.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>, <libc-alpha@sourceware.org>
Subject: Re: RISC-V glibc port, v7
Date: Mon, 29 Jan 2018 22:09:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1801292024540.28694@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CA++6G0BMnJwYpe_ZkUKR5Nj_g3JRFaq+XFGNeeT+V23-=a7aLA@mail.gmail.com>
On Mon, 29 Jan 2018, Andrew Waterman wrote:
> My reading of Annex F is that either the old or new semantics for
> these instructions suffices to implement the C functions, since the
> standard generally leaves signaling-NaN behavior implementation
> defined.
Annex F does not define signaling NaN semantics. TS 18661-1:2014 does,
and is what we follow in glibc. (For example, AArch64 has instructions
with exactly the semantics required to implement fmax and fmin with single
instructions.)
The proposed revision for binding to IEEE 754-2018 keeps fmax and fmin as
in TS 18661-1:2014 (but no longer with an IEEE operation to bind to),
removes fmaxmag and fminmag, and adds new functions fmaximum, fminimum,
fmaximum_mag, fminimum_mag, fmaximum_num, fminimum_num, fmaximum_mag_num
and fminimum_mag_num (along with type-generic macros for them, and
likewise for other floating-point types).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-01-29 20:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 3:58 Palmer Dabbelt
2018-01-27 3:58 ` [PATCH v7 05/17] RISC-V: ABI Implementation Palmer Dabbelt
2018-01-29 16:35 ` Joseph Myers
2018-01-29 16:39 ` Palmer Dabbelt
2018-01-27 3:58 ` [PATCH v7 02/17] Skeleton documentation for the RISC-V port Palmer Dabbelt
2018-02-05 9:19 ` Andreas Schwab
2018-02-08 21:13 ` Palmer Dabbelt
2018-02-08 21:33 ` Jim Wilson
2018-02-12 10:09 ` Andreas Schwab
2018-01-27 3:58 ` [PATCH v7 03/17] Add RISC-V entries to config.h.in Palmer Dabbelt
2018-01-27 8:08 ` [PATCH v7 16/17] Add RISC-V to build-many-glibcs.py Palmer Dabbelt
2018-01-27 8:12 ` [PATCH v7 09/17] RISC-V: Hard Float Support Palmer Dabbelt
2018-01-27 8:13 ` [PATCH v7 17/17] RISC-V: Add ipc_priv.h Palmer Dabbelt
2018-01-27 8:40 ` [PATCH v7 07/17] RISC-V: Thread-Local Storage Support Palmer Dabbelt
2018-07-11 15:28 ` Andreas Schwab
2018-01-27 8:59 ` [PATCH v7 04/17] Add documentation for __riscv_flush_icache Palmer Dabbelt
2018-01-27 9:04 ` [PATCH v7 13/17] RISC-V: Linux Startup and Dynamic Loading Code Palmer Dabbelt
2018-01-27 9:05 ` [PATCH v7 15/17] RISC-V: Build Infastructure Palmer Dabbelt
2018-01-27 9:07 ` [PATCH v7 01/17] sysdeps/init_array: Add PREINIT_FUNCTION to crti.S Palmer Dabbelt
2018-01-27 9:20 ` [PATCH v7 06/17] RISC-V: Startup and Dynamic Loading Code Palmer Dabbelt
2018-01-29 16:36 ` Joseph Myers
2018-01-29 16:56 ` Palmer Dabbelt
2018-01-27 12:12 ` [PATCH v7 08/17] RISC-V: Generic <math.h> and soft-fp Routines Palmer Dabbelt
2018-01-27 12:19 ` [PATCH v7 14/17] RISC-V: Add ABI Lists Palmer Dabbelt
2018-01-27 12:34 ` [PATCH v7 11/17] RISC-V: Linux Syscall Interface Palmer Dabbelt
2018-01-27 12:34 ` [PATCH v7 10/17] RISC-V: Atomic and Locking Routines Palmer Dabbelt
2018-01-27 15:07 ` [PATCH v7 12/17] RISC-V: Linux ABI Palmer Dabbelt
2018-01-27 21:28 ` RISC-V glibc port, v7 Darius Rad
2018-01-29 16:43 ` Joseph Myers
2018-01-29 22:01 ` Palmer Dabbelt
2018-01-29 22:01 ` Andrew Waterman
2018-01-29 22:09 ` Joseph Myers [this message]
2018-01-29 22:09 ` Andrew Waterman
2018-01-29 22:01 ` Palmer Dabbelt
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=alpine.DEB.2.20.1801292024540.28694@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=andrew@sifive.com \
--cc=libc-alpha@sourceware.org \
--cc=palmer@dabbelt.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).