public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz>
To: Jan Hubicka <hubicka@ucw.cz>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] New IPA-CP with real function cloning
Date: Thu, 14 Jul 2011 16:19:00 -0000	[thread overview]
Message-ID: <20110714161150.GB26075@kam.mff.cuni.cz> (raw)
In-Reply-To: <20110714153109.GB1349@virgil.arch.suse.de>

> > >       if (dec < cs->count)
> > > 	cs->count -= dec;
> > >       else
> > > 	cs->count = 0;
> > >     }
> > > 
> > >   if (dump_file)
> > >     dump_profile_updates (orig_node, new_node);
> > > }
> > > 
> > >   if (node->local.can_change_signature)
> > >     {
> > >       args_to_skip = BITMAP_GGC_ALLOC ();
> > >       for (i = 0; i < count; i++)
> > > 	{
> > > 	  tree t = VEC_index (tree, known_vals, i);
> > > 
> > > 	  if ((t && TREE_CODE (t) != TREE_BINFO)
> > > 	      || !ipa_is_param_used (info, i))
> > > 	    bitmap_set_bit (args_to_skip, i);
> > > 	}
> > >     }
> > >   else
> > >     args_to_skip = NULL;
> > When we can't change signature, still we can set is_parm_unused flag for the callee
> > to aid later optimizers.
> 
> I assume I can re-use the node->local.can_change_signature flag?  Is
> that supposed to be set at any given place or can IPA-CP do it on its own?

can_change_signature is currently used by i386 backend and it is set by inliner.
I plan to move it to visibility pass at the time local functions are dentified.
So yes, you can assume it is set and up to date at the time IPA-CP is run.

Honza
> 
> > 
> > Rest of patch looks OK. It definitely reads better than previous ipa-cp.c ;)
> > I suppose we will need to get some experience with the logic deciding whether to clone..
> 
> 
> Thanks, I'll post the current version in a moment.
> 
> Martin

  reply	other threads:[~2011-07-14 16:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23 19:53 Martin Jambor
2011-07-07 16:07 ` Jan Hubicka
2011-07-08 17:37   ` Martin Jambor
2011-07-08 19:07     ` Jan Hubicka
2011-07-14 14:15       ` Martin Jambor
2011-07-14 21:43         ` Jan Hubicka
2011-07-15 13:37           ` Martin Jambor
2011-07-10 19:44 ` Jan Hubicka
2011-07-14 15:41   ` Martin Jambor
2011-07-14 16:19     ` Jan Hubicka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-06-15 15:41 Martin Jambor

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=20110714161150.GB26075@kam.mff.cuni.cz \
    --to=hubicka@ucw.cz \
    --cc=gcc-patches@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).