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 tree-optimization/107837] [10/11/12/13 Regression] Missed optimization: Using memcpy to load a struct unnecessary uses stack space
Date: Wed, 23 Nov 2022 18:06:36 +0000	[thread overview]
Message-ID: <bug-107837-4-4sesUGm71g@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107837-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2022-11-23
            Summary|Missed optimization: Using  |[10/11/12/13 Regression]
                   |memcpy to load a struct     |Missed optimization: Using
                   |unnecessary uses stack      |memcpy to load a struct
                   |space                       |unnecessary uses stack
                   |                            |space
           Keywords|                            |needs-bisection
      Known to work|                            |4.5.3, 4.7.3, 5.1.0, 7.5.0
   Target Milestone|---                         |10.5
      Known to fail|                            |8.1.0
     Ever confirmed|0                           |1

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed, GCC 7 did the right thing ...
Even on the gimple level:

  x$v$0_8 = MEM[(char * {ref-all})src_6(D)];
  x$v$1_9 = MEM[(char * {ref-all})src_6(D) + 8B];
  x$v$2_10 = MEM[(char * {ref-all})src_6(D) + 16B];
  x$v$3_11 = MEM[(char * {ref-all})src_6(D) + 24B];
  _1 = __builtin_bswap64 (x$v$3_11);
  _2 = __builtin_bswap64 (x$v$2_10);
  _3 = __builtin_bswap64 (x$v$1_9);
  _4 = __builtin_bswap64 (x$v$0_8);
  MEM[(struct uint256 *)o_7(D)] = _1;
  MEM[(struct uint256 *)o_7(D) + 8B] = _2;
  MEM[(struct uint256 *)o_7(D) + 16B] = _3;
  MEM[(struct uint256 *)o_7(D) + 24B] = _4;

  reply	other threads:[~2022-11-23 18:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 15:23 [Bug tree-optimization/107837] New: " chfast at gmail dot com
2022-11-23 18:06 ` pinskia at gcc dot gnu.org [this message]
2022-12-02 10:58 ` [Bug tree-optimization/107837] [10/11/12/13 Regression] Missed optimization: Using memcpy to load a struct unnecessary uses stack space since r8-5200 jakub at gcc dot gnu.org
2023-07-07 10:44 ` [Bug tree-optimization/107837] [11/12/13/14 " rguenth 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-107837-4-4sesUGm71g@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).