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 rtl-optimization/112525] fail to eliminate unused store
Date: Tue, 19 Dec 2023 05:18:55 +0000	[thread overview]
Message-ID: <bug-112525-4-E1ZFKqglcP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112525-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jiu Fu Guo <guojiufu@gcc.gnu.org>:

https://gcc.gnu.org/g:4759383245ac97a5c83c0272f0a831f2a26ea5c1

commit r14-6674-g4759383245ac97a5c83c0272f0a831f2a26ea5c1
Author: Jiufu Guo <guojiufu@linux.ibm.com>
Date:   Tue Dec 19 13:03:06 2023 +0800

    treat argp-based mem as frame related in dse

    The issue mentioned in PR112525 would be able to be handled by
    updating dse.cc to treat arg_pointer_rtx similarly with frame_pointer_rtx.
    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30271#c10 also mentioned
    this idea.

    And arpg area may be used to pass argument to callee. So, it would
    be needed to check if call insns are using that mem.

            PR rtl-optimization/112525
            PR target/30271

    gcc/ChangeLog:

            * dse.cc (get_group_info): Add arg_pointer_rtx as frame_related.
            (check_mem_read_rtx): Add parameter to indicate if it is checking
mem
            for call insn.
            (scan_insn): Add mem checking on call usage.

    gcc/testsuite/ChangeLog:

            * gcc.target/powerpc/pr112525.c: New test.
            * gcc.target/powerpc/pr30271.c: New test.

  parent reply	other threads:[~2023-12-19  5:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  6:40 [Bug rtl-optimization/112525] New: " guojiufu at gcc dot gnu.org
2023-11-14  6:48 ` [Bug rtl-optimization/112525] " guojiufu at gcc dot gnu.org
2023-11-14  6:49 ` pinskia at gcc dot gnu.org
2023-11-14  7:01 ` guojiufu at gcc dot gnu.org
2023-11-14  7:44 ` rguenth at gcc dot gnu.org
2023-11-14  7:45 ` rguenth at gcc dot gnu.org
2023-11-15  1:49 ` guojiufu at gcc dot gnu.org
2023-12-19  5:18 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-04  0:47 ` guojiufu 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-112525-4-E1ZFKqglcP@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).