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 r14-2162] Make nomve_fp_1.c require arm_fp
Date: Wed, 28 Jun 2023 13:23:05 +0000 (GMT)	[thread overview]
Message-ID: <20230628132305.21FCD3858D35@sourceware.org> (raw)

https://gcc.gnu.org/g:95cd9913db617051d8201b7cabc79531eed6bd32

commit r14-2162-g95cd9913db617051d8201b7cabc79531eed6bd32
Author: Christophe Lyon <christophe.lyon@linaro.org>
Date:   Wed Jun 28 09:09:04 2023 +0000

    Make nomve_fp_1.c require arm_fp
    
    If GCC is configured with the default (soft) -mfloat-abi, and we don't
    override the target_board test flags appropriately,
    gcc.target/arm/mve/general-c/nomve_fp_1.c fails for lack of
    -mfloat-abi=softfp or -mfloat-abi=hard, because it doesn't use
    dg-add-options arm_v8_1m_mve (on purpose, see comment in the test).
    
    Require and use the options needed for arm_fp to fix this problem.
    
    2023-06-28  Christophe Lyon  <christophe.lyon@linaro.org>
    
            gcc/testsuite/
            * gcc.target/arm/mve/general-c/nomve_fp_1.c: Require arm_fp.

Diff:
---
 gcc/testsuite/gcc.target/arm/mve/general-c/nomve_fp_1.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gcc/testsuite/gcc.target/arm/mve/general-c/nomve_fp_1.c b/gcc/testsuite/gcc.target/arm/mve/general-c/nomve_fp_1.c
index 21c2af16a61..c9d279ead68 100644
--- a/gcc/testsuite/gcc.target/arm/mve/general-c/nomve_fp_1.c
+++ b/gcc/testsuite/gcc.target/arm/mve/general-c/nomve_fp_1.c
@@ -1,9 +1,11 @@
 /* { dg-do compile } */
 /* { dg-require-effective-target arm_v8_1m_mve_ok } */
+/* { dg-require-effective-target arm_fp_ok } */
 /* Do not use dg-add-options arm_v8_1m_mve, because this might expand to "",
    which could imply mve+fp depending on the user settings. We want to make
    sure the '+fp' extension is not enabled.  */
 /* { dg-options "-mfpu=auto -march=armv8.1-m.main+mve" } */
+/* { dg-add-options arm_fp } */
 
 #include <arm_mve.h>

                 reply	other threads:[~2023-06-28 13:23 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=20230628132305.21FCD3858D35@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).