public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: mliska <mliska@suse.cz>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 5/6] Port IPA reference to function_summary infrastructure.
Date: Thu, 09 Jul 2015 17:35:00 -0000	[thread overview]
Message-ID: <559EB0F1.9080006@redhat.com> (raw)
In-Reply-To: <0edaa208a85a7b13e287f21c13a2199f337be53c.1436438929.git.mliska@suse.cz>

On 07/09/2015 03:13 AM, mliska wrote:
> gcc/ChangeLog:
>
> 2015-07-03  Martin Liska  <mliska@suse.cz>
>
> 	* ipa-reference.c (ipa_ref_opt_summary_t): New class.
> 	(get_reference_optimization_summary): Use it.
> 	(set_reference_optimization_summary): Likewise.
> 	(ipa_init): Remove hook holders usage.
> 	(ipa_reference_c_finalize): Likewise.
> 	(ipa_ref_opt_summary_t::duplicate): New function.
> 	(ipa_ref_opt_summary_t::remove): Likewise.
> 	(propagate): Allocate the summary if does not exist.
> 	(ipa_reference_read_optimization_summary): Likewise.
> 	(struct ipa_reference_vars_info_d): Add new method.
> 	(struct ipa_reference_optimization_summary_d): Likewise.
> 	(get_reference_vars_info): Use new underlying container.
> 	(set_reference_vars_info): Remove.
> 	(init_function_info): Set up the container.

> @@ -89,6 +84,13 @@ struct ipa_reference_global_vars_info_d
>
>   struct ipa_reference_optimization_summary_d
>   {
> +  /* Return true if the data structure is empty.  */
> +  inline bool
> +  empty_p ()
> +  {
> +    return statics_not_read == NULL && statics_not_written == NULL;
> +  }
> +
Presumably this is still POD, even with the inline function, so "struct" 
is still correct, right?



> @@ -99,6 +101,14 @@ typedef struct ipa_reference_optimization_summary_d *ipa_reference_optimization_
>
>   struct ipa_reference_vars_info_d
>   {
> +  /* Return true if the data structure is empty.  */
> +  inline bool
> +  empty_p ()
> +  {
> +    return local.statics_read == NULL && local.statics_written == NULL
> +      && global.statics_read == NULL && global.statics_written == NULL;
> +  }
> +
Similarly.

So please confirm those are still POD types.  If they are, then the 
patch is OK as-is.  If they're not PODs, then change them to classes and 
that patch is pre-approved.

jeff

  reply	other threads:[~2015-07-09 17:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 11:07 [PATCH 0/6] {function,edge}_summary for IPA passes mliska
2015-07-09 11:07 ` [PATCH 1/6] hash_set: add iterator and remove method mliska
2015-07-09 17:05   ` Jeff Law
2015-07-09 11:08 ` [PATCH 3/6] IPA inline: port inline_edge_summary to a new infrastructure mliska
2015-07-09 17:21   ` Jeff Law
2015-07-09 11:08 ` [PATCH 5/6] Port IPA reference to function_summary infrastructure mliska
2015-07-09 17:35   ` Jeff Law [this message]
2015-07-09 20:46     ` Martin Liška
2015-07-10 13:30   ` Martin Jambor
2015-07-16 14:14     ` Martin Liška
2015-07-09 11:08 ` [PATCH 2/6] Introduce new edge_summary class and replace ipa_edge_args_sum mliska
2015-07-09 17:15   ` Jeff Law
2015-07-09 20:45     ` Martin Liška
2015-07-10 13:31   ` Martin Jambor
2015-07-16 14:06     ` Martin Liška
2015-08-03 15:22       ` Martin Liška
2015-07-09 11:08 ` [PATCH 4/6] Port ipa-cp to use cgraph_edge summary mliska
2015-07-09 17:39   ` Jeff Law
2015-07-10 14:18   ` Martin Jambor
2015-07-16 14:08     ` Martin Liška
2015-07-09 11:09 ` [PATCH 6/6] Migrate ipa-pure-const to function_summary mliska
2015-07-09 17:44   ` Jeff Law
2015-07-09 20:47     ` Martin Liška
2015-07-16 14:17       ` Martin Liška

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=559EB0F1.9080006@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mliska@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).