From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-alpha@sourceware.org
Cc: fweimer@redhat.com, joseph@codesourcery.com
Subject: [PATCH 0/2] unnormal test case fixes
Date: Mon, 4 Jan 2021 19:54:41 +0530 [thread overview]
Message-ID: <20210104142443.3034204-1-siddhesh@sourceware.org> (raw)
The following two patches fix issues that Joseph pointed out in the
unnormal tests.
The first patch fixes the breakage caused by moving nan-pseudo-number.h
and in the process also fixes the macro condition used to limit
conditions under which the test is built.
The second patch limits the macro condition further so that the unnormal
tests build only for long double and Float64x on intel96. Further, it
cleans up the test macro names and casts test arguments to the type
being tested.
Verified with build-many-glibcs.py for ia64, m68k, i686 and aarch64 and
with a native build and test for x86_64. Florian is helping me with a
full build-many-glibcs.py run since I don't have compilers for all
architectures yet.
Siddhesh Poyarekar (2):
Drop nan-pseudo-number.h usage from tests
Limit unnormal tests to supported long double formats
math/libm-test-driver.c | 17 +++++++++--------
math/libm-test-fpclassify.inc | 18 +++++++++---------
math/libm-test-isinf.inc | 18 +++++++++---------
math/libm-test-isnan.inc | 18 +++++++++---------
math/libm-test-issignaling.inc | 18 +++++++++---------
math/libm-test-support.h | 2 ++
math/test-float64x.h | 1 +
math/test-ldouble.h | 1 +
sysdeps/ieee754/ldbl-96/nan-pseudo-number.h | 4 +---
sysdeps/x86/fpu/nan-pseudo-number.h | 1 -
10 files changed, 50 insertions(+), 48 deletions(-)
--
2.29.2
next reply other threads:[~2021-01-04 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 14:24 Siddhesh Poyarekar [this message]
2021-01-04 14:24 ` [PATCH 1/2] Drop nan-pseudo-number.h usage from tests Siddhesh Poyarekar
2021-01-04 14:29 ` Florian Weimer
2021-01-04 14:37 ` Siddhesh Poyarekar
2021-01-04 15:13 ` Szabolcs Nagy
2021-01-04 15:21 ` Siddhesh Poyarekar
2021-01-04 15:17 ` Florian Weimer
2021-01-04 15:21 ` Siddhesh Poyarekar
2021-01-04 14:24 ` [PATCH 2/2] Limit unnormal tests to supported long double formats Siddhesh Poyarekar
2021-01-12 7:22 ` [PING][PATCH " Siddhesh Poyarekar
2021-01-12 18:21 ` Joseph Myers
2021-01-13 4:38 ` [PATCH v2] Use the right argument code in unnormal tests Siddhesh Poyarekar
2021-01-13 17:41 ` 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=20210104142443.3034204-1-siddhesh@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@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).