From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Cgraph alias reorg 8/14 (ipa-cp and ipa-prop update)
Date: Tue, 12 Jul 2011 12:23:00 -0000 [thread overview]
Message-ID: <619469B7-4F86-4D38-BC20-739679FEA81B@codesourcery.com> (raw)
In-Reply-To: <20110610145543.GF28776@kam.mff.cuni.cz>
On Jun 10, 2011, at 6:55 PM, Jan Hubicka wrote:
> Hi,
> this patch updated ipa-cp and ipa-prop for aliases. It is basically easy - we don't
> analyze nodes represneting aliases and when propagating we skip them, like everywhere
> else.
...
> @@ -759,7 +768,8 @@ ipcp_propagate_stage (void)
>
> for (cs = node->callees; cs; cs = cs->next_callee)
> {
> - struct ipa_node_params *callee_info = IPA_NODE_REF (cs->callee);
> + struct cgraph_node *callee = cgraph_function_or_thunk_node (cs->callee, NULL);
> + struct ipa_node_params *callee_info = IPA_NODE_REF (callee);
> struct ipa_edge_args *args = IPA_EDGE_REF (cs);
>
> if (ipa_is_called_with_var_arguments (callee_info)
> @@ -778,11 +788,11 @@ ipcp_propagate_stage (void)
> {
> dest_lat->type = new_lat.type;
> dest_lat->constant = new_lat.constant;
> - ipa_push_func_to_list (&wl, cs->callee);
> + ipa_push_func_to_list (&wl, callee);
> }
>
> if (ipcp_propagate_types (info, callee_info, jump_func, i))
> - ipa_push_func_to_list (&wl, cs->callee);
> + ipa_push_func_to_list (&wl, callee);
> }
> }
> }
Jan,
I have a question about the above hunk. With this hunk you replace all uses of 'cs->callee' with 'callee' in ipcp_propagate_stage() except for in the check:
if (ipa_is_called_with_var_arguments (callee_info)
|| !cs->callee->analyzed
|| ipa_is_called_with_var_arguments (callee_info))
continue;
Is there a reason why you left 'cs->callee' intact in this case?
Thank you,
--
Maxim Kuvyrkov
CodeSourcery / Mentor Graphics
prev parent reply other threads:[~2011-07-12 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 15:42 Jan Hubicka
2011-06-13 17:54 ` Martin Jambor
2011-06-13 19:44 ` Jan Hubicka
2011-06-14 13:19 ` Jan Hubicka
2011-07-12 12:23 ` Maxim Kuvyrkov [this message]
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=619469B7-4F86-4D38-BC20-739679FEA81B@codesourcery.com \
--to=maxim@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.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).