public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89252] Vector load/store aren't used to initialize large memory
Date: Sun, 01 Aug 2021 16:59:04 +0000	[thread overview]
Message-ID: <bug-89252-4-428fCVQ3mZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89252-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
          Component|middle-end                  |target
             Target|                            |x86_64-linux-gnu

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
On the trunk we get:
        movdqa  xmm0, XMMWORD PTR _ZL5array[rip]
        movdqa  xmm1, XMMWORD PTR _ZL5array[rip+16]
        movdqa  xmm2, XMMWORD PTR _ZL5array[rip+32]
        movdqa  xmm3, XMMWORD PTR _ZL5array[rip+48]
        movdqa  xmm4, XMMWORD PTR _ZL5array[rip+64]
        movdqa  xmm5, XMMWORD PTR _ZL5array[rip+80]
        movups  XMMWORD PTR [rdi], xmm0
        movdqa  xmm6, XMMWORD PTR _ZL5array[rip+96]
        movdqa  xmm7, XMMWORD PTR _ZL5array[rip+112]
        movups  XMMWORD PTR [rdi+16], xmm1
        movups  XMMWORD PTR [rdi+32], xmm2
        movups  XMMWORD PTR [rdi+48], xmm3
        movups  XMMWORD PTR [rdi+320], xmm4
        movups  XMMWORD PTR [rdi+336], xmm5
        movups  XMMWORD PTR [rdi+352], xmm6
        movups  XMMWORD PTR [rdi+368], xmm7

Even with -mavx which I had assumed would use the ymm registers.

       reply	other threads:[~2021-08-01 16:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89252-4@http.gcc.gnu.org/bugzilla/>
2021-08-01 16:59 ` pinskia at gcc dot gnu.org [this message]
2021-08-01 17:20 ` hjl.tools at gmail dot com

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-89252-4-428fCVQ3mZ@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).