public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109667] [12/13/14 Regression] Unnecessary temporary storage used for 32-byte struct
Date: Tue, 02 May 2023 09:56:01 +0000	[thread overview]
Message-ID: <bug-109667-4-mxUuOrk83c@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109667-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So, either SRA should be tweaked so that it can deal with DSE trimming of
initializations (I think that is the best way forward, after all, user could
have
done it manually too -
struct i256 {
    long v[4];
};
void assign(struct i256 *v, long z) {
    struct i256 r;
    __builtin_memset (&r.v[1], 0, sizeof (long) * 3);
    for (int i = 0; i < 1; ++i) 
        r.v[i] = z;
    *v = r;
}
regressed with r7-2588-gdf7ec09f1209a33b35 ), or we should do something at the
RTL level  like it apparently worked before the r7-2588 change, or we should
disable trimming in the DSE part before SRA.

  parent reply	other threads:[~2023-05-02  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 11:46 [Bug tree-optimization/109667] New: " chfast at gmail dot com
2023-04-28 12:27 ` [Bug tree-optimization/109667] " rguenth at gcc dot gnu.org
2023-05-02  9:45 ` jakub at gcc dot gnu.org
2023-05-02  9:56 ` jakub at gcc dot gnu.org [this message]
2023-05-08 12:27 ` 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-109667-4-mxUuOrk83c@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).