From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Christophe Lyon <christophe.lyon@foss.st.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] testsuite: Make sure double-precision is supported in g++.dg/eh/arm-vfp-unwind.C
Date: Wed, 15 Sep 2021 12:02:39 +0100 [thread overview]
Message-ID: <7788bf43-7afc-59d6-7995-c6fb4ad6eefb@foss.arm.com> (raw)
In-Reply-To: <20210826155310.4039951-1-christophe.lyon@foss.st.com>
On 26/08/2021 16:53, Christophe Lyon via Gcc-patches wrote:
> g++.dg/eh/arm-vfp-unwind.C uses an asm statement relying on
> double-precision FPU support, but does not make sure it is actually
> supported by the target.
> Check (__ARM_FP & 8) to ensure this.
>
> 2021-08-26 Christophe Lyon <christophe.lyon@foss.st.com>
>
> gcc/testsuite/
> * g++.dg/eh/arm-vfp-unwind.C: Check __ARM_FP.
> ---
> gcc/testsuite/g++.dg/eh/arm-vfp-unwind.C | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/g++.dg/eh/arm-vfp-unwind.C b/gcc/testsuite/g++.dg/eh/arm-vfp-unwind.C
> index 62263c0c3b0..90d20081d78 100644
> --- a/gcc/testsuite/g++.dg/eh/arm-vfp-unwind.C
> +++ b/gcc/testsuite/g++.dg/eh/arm-vfp-unwind.C
> @@ -3,7 +3,7 @@
>
> /* Test to catch off-by-one errors in arm/pr-support.c. */
>
> -#if defined (__VFP_FP__) && !defined (__SOFTFP__)
> +#if defined (__VFP_FP__) && !defined (__SOFTFP__) && (__ARM_FP & 8)
>
> #include <iostream>
> #include <stdlib.h>
>
Wouldn't it be better to have an alternate to the asm for the case where
we only have single-precision float? Something like (untested):
static void donkey ()
{
#if __ARM_FP & 8
asm volatile ("fcpyd d9, %P0" : : "w" (1.2345) : "d9");
#else
asm volatile ("fcpys s18, %P0" : : "w" (1.2345f) : "s18");
#endif
throw 1;
}
R.
next prev parent reply other threads:[~2021-09-15 11:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 15:53 Christophe Lyon
2021-09-06 7:23 ` Christophe LYON
2021-09-13 7:52 ` Christophe LYON
2021-09-15 11:02 ` Richard Earnshaw [this message]
2021-09-15 12:26 ` Christophe LYON
2021-09-15 12:49 ` Richard Earnshaw
2021-09-15 16:13 ` Christophe Lyon
2021-09-15 16:43 ` Richard Earnshaw
2021-09-16 9:12 ` Christophe LYON
2021-09-16 9:19 ` Richard Earnshaw
2021-09-16 9:35 ` Christophe Lyon
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=7788bf43-7afc-59d6-7995-c6fb4ad6eefb@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=christophe.lyon@foss.st.com \
--cc=gcc-patches@gcc.gnu.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).