public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Christophe Lyon <clyon@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r11-7795] testsuite/arm: Add arm_hard_ok check in armv8_2-fp16-scalar-2.c
Date: Tue, 23 Mar 2021 15:13:00 +0000 (GMT)	[thread overview]
Message-ID: <20210323151300.EF3CB385041F@sourceware.org> (raw)

https://gcc.gnu.org/g:1843341b12933a86380cc201c845cb9d732a377f

commit r11-7795-g1843341b12933a86380cc201c845cb9d732a377f
Author: Christophe Lyon <christophe.lyon@linaro.org>
Date:   Sun Apr 26 18:56:11 2020 +0000

    testsuite/arm: Add arm_hard_ok check in armv8_2-fp16-scalar-2.c
    
    This test relies on -mfloat-abi=hard to pass (otherwise
    test_mov_imm_[12] directly build the 1.0 fp16 representation via movw
    r0, #15360 rather than using vmov.f16 s0, #1.0e+0 as expected by
    scan-assembler-times)
    
    Adding the arm_hard_ok check makes the test unsupported eg. on
    arm-linux-gnueabi instead of reporting a failure.
    
    2021-03-20  Christophe Lyon  <christophe.lyon@linaro.org>
    
            gcc/testsuite/
            * gcc.target/arm/armv8_2-fp16-scalar-2.c: Add arm_hard_ok.

Diff:
---
 gcc/testsuite/gcc.target/arm/armv8_2-fp16-scalar-2.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gcc/testsuite/gcc.target/arm/armv8_2-fp16-scalar-2.c b/gcc/testsuite/gcc.target/arm/armv8_2-fp16-scalar-2.c
index fa4828df064..de5adf30dd8 100644
--- a/gcc/testsuite/gcc.target/arm/armv8_2-fp16-scalar-2.c
+++ b/gcc/testsuite/gcc.target/arm/armv8_2-fp16-scalar-2.c
@@ -1,7 +1,9 @@
 /* { dg-do compile }  */
+/* { dg-require-effective-target arm_hard_ok }  */
 /* { dg-require-effective-target arm_v8_2a_fp16_scalar_ok }  */
 /* { dg-options "-O2 -std=c11" }  */
 /* { dg-add-options arm_v8_2a_fp16_scalar }  */
+/* { dg-additional-options "-mfloat-abi=hard" } */
 
 /* Test compiler use of FP16 instructions.  */
 #include <arm_fp16.h>


                 reply	other threads:[~2021-03-23 15:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210323151300.EF3CB385041F@sourceware.org \
    --to=clyon@gcc.gnu.org \
    --cc=gcc-cvs@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).