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/112930] gcc.target/aarch64/sme/call_sm_switch_7.c ICEs on  aarch64_be
Date: Sun, 10 Dec 2023 19:46:38 +0000	[thread overview]
Message-ID: <bug-112930-4-x9uoTbRDpk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112930-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>:

https://gcc.gnu.org/g:f5c8d6bc050a8a6120aff2be25b6892d91baac99

commit r14-6386-gf5c8d6bc050a8a6120aff2be25b6892d91baac99
Author: Richard Sandiford <richard.sandiford@arm.com>
Date:   Sun Dec 10 19:46:06 2023 +0000

    aarch64: Fix SMSTART/SMSTOP save/restore for BE

    VNx16QI (the SVE register byte mode) is the only SVE mode for which
    LD1 and LDR result in the same register layout for big-endian.  It is
    therefore the only mode for which we allow LDR and STR to be used for
    big-endian SVE moves.

    The SME support sometimes needs to use LDR and STR to save and restore
    Z register contents around an SMSTART/SMSTOP SM.  It therefore needs
    to use VNx16QI regardless of the type of value that is stored in the
    Z registers.

    gcc/
            PR target/112930
            * config/aarch64/aarch64.cc
(aarch64_sme_mode_switch_regs::add_reg):
            Force specific SVE modes for single registers as well as
structures.

  parent reply	other threads:[~2023-12-10 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-09  2:11 [Bug target/112930] New: " pinskia at gcc dot gnu.org
2023-12-09  2:12 ` [Bug target/112930] " pinskia at gcc dot gnu.org
2023-12-09 17:07 ` rsandifo at gcc dot gnu.org
2023-12-10 19:46 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-10 19:56 ` rsandifo 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-112930-4-x9uoTbRDpk@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).