public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/114800] redundant set-zero when initiate a struct
Date: Mon, 22 Apr 2024 09:10:26 +0000	[thread overview]
Message-ID: <bug-114800-4-QBlW9Jaadf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114800-4@http.gcc.gnu.org/bugzilla/>

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

Xi Ruoyao <xry111 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xry111 at gcc dot gnu.org

--- Comment #1 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to absoler from comment #0)

> such code is compiled as: (gcc-13.2.0 -O2, regression [11/12/13/trunk])

The regression marker isn't true.  It looks like the redundant zeroing has been
there even in GCC 4.8.1.  GCC 4.7 fails to compile the test case.

And IIRC there is already an report complaining some redundant zeroing like
this...

  reply	other threads:[~2024-04-22  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22  8:27 [Bug rtl-optimization/114800] New: " absoler at smail dot nju.edu.cn
2024-04-22  9:10 ` xry111 at gcc dot gnu.org [this message]
2024-04-22 23:33 ` [Bug tree-optimization/114800] " pinskia at gcc dot gnu.org
2024-04-22 23:35 ` [Bug tree-optimization/114800] DSE does not remove set-zero which is partial redundant pinskia at gcc dot gnu.org
2024-04-22 23:40 ` [Bug tree-optimization/114800] DSE does not remove set-zero which is partial redundant with respect to mod-ref pinskia 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-114800-4-QBlW9Jaadf@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).