From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v4] testsuite: Sanitize fails for SP FPU on Arm
Date: Thu, 20 Oct 2022 21:06:32 +0200 [thread overview]
Message-ID: <7860f8df-bd1d-3464-3b67-300d9357f858@foss.st.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2210201818410.71947@digraph.polyomino.org.uk>
On 2022-10-20 20:19, Joseph Myers wrote:
> On Wed, 19 Oct 2022, Torbjörn SVENSSON via Gcc-patches wrote:
>
>> This patch stops reporting fails for Arm targets with single
>> precision floating point unit for types wider than 32 bits (the width
>> of float on arm-none-eabi).
>>
>> As reported in PR102017, fenv is reported as supported in recent
>> versions of newlib. At the same time, for some Arm targets, the
>> implementation in libgcc does not support exceptions and thus, the
>> test fails with a call to abort().
>
> This patch is OK.
>
Thanks Joseph!
Pushed.
prev parent reply other threads:[~2022-10-20 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 14:19 Torbjörn SVENSSON
2022-10-20 18:19 ` Joseph Myers
2022-10-20 19:06 ` Torbjorn SVENSSON [this message]
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=7860f8df-bd1d-3464-3b67-300d9357f858@foss.st.com \
--to=torbjorn.svensson@foss.st.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@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).