public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/105638] Redundant stores aren't removed by DSE
Date: Wed, 01 Jun 2022 21:23:39 +0000	[thread overview]
Message-ID: <bug-105638-4-i3ZboYe7ry@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105638-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:

https://gcc.gnu.org/g:a743a72714fc4a9d7036d28d0cacdf2a3621f629

commit r13-921-ga743a72714fc4a9d7036d28d0cacdf2a3621f629
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Wed May 18 13:00:47 2022 -0700

    DSE: Use the constant store source if possible

    RTL DSE tracks redundant constant stores within a basic block.  When RTL
    loop invariant motion hoists a constant initialization out of the loop
    into a separate basic block, the constant store value becomes unknown
    within the original basic block.  When recording store for RTL DSE, check
    if the source register is set only once to a constant by a non-partial
    unconditional load.  If yes, record the constant as the constant store
    source.  It eliminates unrolled zero stores after memset 0 in a loop
    where a vector register is used as the zero store source.

    gcc/

            PR rtl-optimization/105638
            * df-core.cc (df_find_single_def_src): Moved and renamed from
            find_single_def_src in loop-iv.cc.  Change the argument to rtx
            and use rtx_equal_p.  Return null for partial or conditional
            defs.
            * df.h (df_find_single_def_src): New prototype.
            * dse.cc (record_store): Use the constant source if the source
            register is set only once.
            * loop-iv.cc (find_single_def_src): Moved to df-core.cc.
            (replace_single_def_regs): Replace find_single_def_src with
            df_find_single_def_src.

    gcc/testsuite/

            PR rtl-optimization/105638
            * g++.target/i386/pr105638.C: New test.

  parent reply	other threads:[~2022-06-01 21:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 23:29 [Bug middle-end/105638] New: " hjl.tools at gmail dot com
2022-05-18 12:42 ` [Bug middle-end/105638] " rguenth at gcc dot gnu.org
2022-06-01 21:23 ` cvs-commit at gcc dot gnu.org [this message]
2022-06-14 13:53 ` 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-105638-4-i3ZboYe7ry@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).