public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99773] ARM v8.1-m MVE interaction with -mfloat-abi not clear
Date: Tue, 30 Mar 2021 13:11:33 +0000	[thread overview]
Message-ID: <bug-99773-4-gqGW48hjPb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99773-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99773

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Christophe Lyon <clyon@gcc.gnu.org>:

https://gcc.gnu.org/g:6f93a7c7fc62b2d6ab47e5d5eb60d41366e1ee9e

commit r11-7908-g6f93a7c7fc62b2d6ab47e5d5eb60d41366e1ee9e
Author: Christophe Lyon <christophe.lyon@linaro.org>
Date:   Tue Mar 30 12:26:33 2021 +0000

    arm: Fix emission of Tag_ABI_VFP_args with MVE and -mfloat-abi=hard (PR
target/99773)

    When compiling with -mfloat-abi=hard -march=armv8.1-m.main+mve, we
    want to emit Tag_ABI_VFP_args even though we are not emitting
    floating-point instructions (we need "+mve.fp" for that), because we
    use MVE registers to pass FP arguments.

    This patch removes the condition on (! TARGET_SOFT_FLOAT) because this
    is a case where TARGET_SOFT_FLOAT is true, and TARGET_HARD_FLOAT_ABI
    is true too.

    2021-03-30  Richard Earnshaw  <rearnsha@arm.com>

            gcc/
            PR target/99773
            * config/arm/arm.c (arm_file_start): Fix emission of
            Tag_ABI_VFP_args attribute.

  parent reply	other threads:[~2021-03-30 13:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 16:26 [Bug target/99773] New: " clyon at gcc dot gnu.org
2021-03-25 16:49 ` [Bug target/99773] " rearnsha at gcc dot gnu.org
2021-03-25 16:58 ` acoplan at gcc dot gnu.org
2021-03-25 17:57 ` clyon at gcc dot gnu.org
2021-03-26 11:23 ` rearnsha at gcc dot gnu.org
2021-03-26 14:27 ` clyon at gcc dot gnu.org
2021-03-30 13:11 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-30 13:12 ` clyon at gcc dot gnu.org

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=bug-99773-4-gqGW48hjPb@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).