public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guojiufu 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: Wed, 15 Nov 2023 01:49:14 +0000 [thread overview]
Message-ID: <bug-112525-4-9tuaKkEbP9@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 #6 from Jiu Fu Guo <guojiufu at gcc dot gnu.org> ---
(In reply to Jiu Fu Guo from comment #3)
> One possible method is fixing DSE to let is able to remove those 'store's.
> (but need to take care of the case that is using 'arg_pointer' to pass
> parameters.)
>
Some 'store's to the incoming argument area (arg_pointer_rtx) may not safe to
be removed:
For example: call memset on X86_64 , the insn(s) maybe:
134: [argp+0x8]=r134:SI
135: [argp+0x4]=0x1
136: [argp]=r132:SI
137: ax:SI=call [`memset'] argc:0xc
REG_CALL_DECL `memset'
REG_EH_REGION 0
insn(s) 134/135/136 can not be removed.
next prev parent reply other threads:[~2023-11-15 1:49 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 [this message]
2023-12-19 5:18 ` cvs-commit at gcc dot gnu.org
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-9tuaKkEbP9@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).