From: Joseph Myers <joseph@codesourcery.com>
To: Siddhesh Poyarekar <siddhesh@sourceware.org>
Cc: <libc-alpha@sourceware.org>, <fweimer@redhat.com>
Subject: Re: [PATCH v3 1/2] x86 long double: Consider pseudo numbers as signaling
Date: Thu, 31 Dec 2020 22:58:13 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2012312255570.929441@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20201224024554.3579622-2-siddhesh@sourceware.org>
On Thu, 24 Dec 2020, Siddhesh Poyarekar via Libc-alpha wrote:
> diff --git a/sysdeps/generic/nan-pseudo-number.h b/sysdeps/generic/nan-pseudo-number.h
I don't think this belongs in sysdeps/generic/. The "pseudo-number"
concept is specific to the ldbl-96 format; a "generic" header is really
something specific to ldbl-96 and so should go in sysdeps/ieee754/ldbl-96/
instead. (x86 and m68k have different rules regarding what encodings are
valid. ia64 manuals seem to suggest that only a subset of the encodings
that are invalid on x86 are also invalid on ia64 but I don't have access
to hardware to test.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-12-31 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 2:45 [PATCH v3 0/2] x86 pseudo-normal numbers Siddhesh Poyarekar
2020-12-24 2:45 ` [PATCH v3 1/2] x86 long double: Consider pseudo numbers as signaling Siddhesh Poyarekar
2020-12-28 16:57 ` Adhemerval Zanella
2020-12-30 5:31 ` [COMMITTED] " Siddhesh Poyarekar
2020-12-31 22:58 ` Joseph Myers [this message]
2020-12-31 23:23 ` [PATCH v3 1/2] " Andreas Schwab
2021-01-04 9:30 ` [COMMITTED] Move generic nan-pseudo-number.h to ldbl-96 Siddhesh Poyarekar
2020-12-24 2:45 ` [PATCH v3 2/2] x86 long double: Add tests for pseudo normal numbers Siddhesh Poyarekar
2020-12-28 17:04 ` Adhemerval Zanella
2020-12-31 23:09 ` Joseph Myers
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.22.394.2012312255570.929441@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@sourceware.org \
/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).