public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100000] non-leaf epologue/prologue used if MVE v4sf is used for load/return
Date: Wed, 25 Jan 2023 17:50:26 +0000	[thread overview]
Message-ID: <bug-100000-4-v9KbCGRj6t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100000-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Given that the hard-float ABI essentially requires V4SF as a type, it might be
better to consider this mode supported unconditionally in this case, and
although that might make the compiler try some pointless vectorizations it
would generate better code for cases like this.

  parent reply	other threads:[~2023-01-25 17:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 14:43 [Bug target/100000] New: arm: Missed optimisation storing V4DF vector acoplan at gcc dot gnu.org
2021-04-10 20:16 ` [Bug target/100000] non-leaf epologue/prologue used if MVE v4sf is used for load/return pinskia at gcc dot gnu.org
2021-12-09  1:32 ` pinskia at gcc dot gnu.org
2023-01-25 17:45 ` rearnsha at gcc dot gnu.org
2023-01-25 17:50 ` rearnsha at gcc dot gnu.org [this message]
2023-03-09 15:27 ` stammark 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-100000-4-v9KbCGRj6t@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).