From: Christophe LYON <christophe.lyon@foss.st.com>
To: gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] testsuite: Make sure double-precision is supported in g++.dg/eh/arm-vfp-unwind.C
Date: Mon, 13 Sep 2021 09:52:56 +0200 [thread overview]
Message-ID: <8856591e-e18d-a1d8-9dda-9a156562fea8@foss.st.com> (raw)
In-Reply-To: <5d96c18c-4248-b1cf-c4a9-64a5e85a9406@foss.st.com>
ping?
On 06/09/2021 09:23, Christophe LYON wrote:
> ping?
>
> On 26/08/2021 17:53, Christophe Lyon 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>
next prev parent reply other threads:[~2021-09-13 7:53 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 [this message]
2021-09-15 11:02 ` Richard Earnshaw
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=8856591e-e18d-a1d8-9dda-9a156562fea8@foss.st.com \
--to=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).