From: Florian Weimer <fweimer@redhat.com>
To: Siddhesh Poyarekar <siddhesh@sourceware.org>
Cc: libc-alpha@sourceware.org, joseph@codesourcery.com
Subject: Re: [PATCH 1/2] Drop nan-pseudo-number.h usage from tests
Date: Mon, 04 Jan 2021 15:29:42 +0100 [thread overview]
Message-ID: <87pn2klqqx.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20210104142443.3034204-2-siddhesh@sourceware.org> (Siddhesh Poyarekar's message of "Mon, 4 Jan 2021 19:54:42 +0530")
* Siddhesh Poyarekar:
> Make the tests use TEST_COND_intel96 to decide on whether to build the
> unnormal tests instead of the macro in nan-pseudo-number.h and then
> drop the header inclusion. This unbreaks test runs on all
> architectures that do not have ldbl-96.
>
> Also drop the HANDLE_PSEUDO_NUMBERS macro since it is not used
> anywhere.
Is this identical to the patch you shared previously? Then it fixes the
build at least, so please push this.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2021-01-04 14:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 14:24 [PATCH 0/2] unnormal test case fixes Siddhesh Poyarekar
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 [this message]
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=87pn2klqqx.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=joseph@codesourcery.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).