From: Feng Xue OS <fxue@os.amperecomputing.com>
To: luoxhu <luoxhu@linux.ibm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jan Hubicka <hubicka@ucw.cz>, Martin Jambor <mjambor@suse.cz>
Subject: Re: [PATCH] Support multi-versioning on self-recursive function (ipa/92133)
Date: Fri, 18 Oct 2019 05:15:00 -0000 [thread overview]
Message-ID: <BYAPR01MB4869AD061017355A373F6E4DF76C0@BYAPR01MB4869.prod.exchangelabs.com> (raw)
In-Reply-To: <ca6dc810-560e-47aa-5f99-54289ce74369@linux.ibm.com>
> I noticed similar issue when analyzing the SPEC, self-recursive function is
> not versioned and posted my observations in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92074.
> Generally, this could be implemented well by your patch, while I am
> wondering whether it is OK to convert the recursive function to
> non-recursive function in a independent pass after ipa-cp and ipa-sra instead
> of reuse the ipa-cp framework?
> The reason is sometimes the argument is passed-by-reference, and
> ipa-sra runs after ipa-cp, so this kind of optimization may not be done in
> WPA. What's your idea about this, please? Thanks.
Function versioning is done in ipa-cp, there is nothing special for recursive function.
So adding a dedicated pass for recursive seems to be redundant.
We might not need to resort to ipa-sra to resolve concern you mentioned. Original
ipa-cp already supports a simple kind of propagation on by-ref argument, who must
be defined by constant. And for an extended form as: *arg = *param OP constant, I've
created a tracker PR91682, also composed a patch:
https://gcc.gnu.org/ml/gcc-patches/2019-09/msg01189.html.
Feng
next prev parent reply other threads:[~2019-10-18 3:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 8:35 Feng Xue OS
2019-10-18 2:12 ` luoxhu
2019-10-18 5:15 ` Feng Xue OS [this message]
2019-10-24 6:17 ` luoxhu
2019-10-24 6:57 ` Feng Xue OS
2019-11-14 13:29 ` Jan Hubicka
2019-11-14 15:16 ` Feng Xue OS
2019-11-14 15:28 ` Jan Hubicka
2019-11-14 16:02 ` Feng Xue OS
2019-11-14 20:50 ` Jan Hubicka
2019-11-15 15:37 ` Feng Xue OS
2019-11-22 5:26 ` Ping: " Feng Xue OS
2019-11-22 11:34 ` Martin Jambor
2019-11-25 14:17 ` Feng Xue OS
2019-11-27 2:07 ` Feng Xue OS
2019-11-27 15:12 ` Jan Hubicka
2019-11-28 3:48 ` Feng Xue OS
2019-12-01 23:20 ` Jeff Law
2019-12-02 7:07 ` Feng Xue OS
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=BYAPR01MB4869AD061017355A373F6E4DF76C0@BYAPR01MB4869.prod.exchangelabs.com \
--to=fxue@os.amperecomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=luoxhu@linux.ibm.com \
--cc=mjambor@suse.cz \
/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).