public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "liuhongt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112992] Inefficient vector initialization using vec_duplicate/broadcast
Date: Wed, 13 Dec 2023 07:42:04 +0000	[thread overview]
Message-ID: <bug-112992-4-WSISg1WKzM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112992-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Hongtao Liu <liuhongt at gcc dot gnu.org> ---
(In reply to Hongtao Liu from comment #6)
> > Thoughts?  Apologies if this is a dup.  I'm happy to work up a patch if
> > someone could advise on where best this should be fixed.  Perhaps RTL's
> > vec_duplicate could be canonicalized to the most appropriate vector mode?
> That may breaks avx512 embedded broadcast.

But perhaps we can add some postreload splitter to check for load from memory
or broadcast from memeory to see if we can use the smallest constant pool.

  parent reply	other threads:[~2023-12-13  7:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13  0:18 [Bug target/112992] New: " roger at nextmovesoftware dot com
2023-12-13  0:22 ` [Bug target/112992] " pinskia at gcc dot gnu.org
2023-12-13  0:28 ` pinskia at gcc dot gnu.org
2023-12-13  1:25 ` liuhongt at gcc dot gnu.org
2023-12-13  1:26 ` liuhongt at gcc dot gnu.org
2023-12-13  2:44 ` liuhongt at gcc dot gnu.org
2023-12-13  2:46 ` liuhongt at gcc dot gnu.org
2023-12-13  7:42 ` liuhongt at gcc dot gnu.org [this message]
2023-12-14  8:41 ` cvs-commit at gcc dot gnu.org
2024-01-09  8:33 ` cvs-commit at gcc dot gnu.org
2024-01-14 11:51 ` roger at nextmovesoftware dot com
2024-05-07  6:19 ` cvs-commit 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-112992-4-WSISg1WKzM@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).