public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Jambor <mjambor@suse.cz>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: Andrew MacLeod <amacleod@redhat.com>,
	GCC patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Provide an API for ipa_vr.
Date: Wed, 24 May 2023 16:10:25 +0200	[thread overview]
Message-ID: <ri68rddddm6.fsf@suse.cz> (raw)
In-Reply-To: <20230517141622.464538-1-aldyh@redhat.com>

Hello,

On Wed, May 17 2023, Aldy Hernandez wrote:
> This patch encapsulates the ipa_vr internals into an API.  It also
> makes it type agnostic, in preparation for upcoming changes to IPA.
>
> Interestingly, there's a 0.44% improvement to IPA-cp, which I'm sure
> we'll soak up with future changes in this area :).
>
> BTW, there's a note here:
> +  // vrange_storage is typeless, but we need to know what type of
> +  // range that is being streamed out (irange, frange, etc).  AFAICT,
> +  // there's no way to get at the underlying type by the time we
> +  // stream out in write_ipcp_transformation_info.
> +  tree m_type;
>
> Could someone more IPA savvy double check this is indeed the case?

Yes, that is true and keeping the type around in ipa_vr is probably
easier than postponing the deallocation of parameter descriptors
somehow.

>
> OK for trunk?

Yes, thanks.

Martin

>
> gcc/ChangeLog:
>
> 	* ipa-cp.cc (ipa_value_range_from_jfunc): Use new ipa_vr API.
> 	(ipcp_store_vr_results): Same.
> 	* ipa-prop.cc (ipa_vr::ipa_vr): New.
> 	(ipa_vr::get_vrange): New.
> 	(ipa_vr::set_unknown): New.
> 	(ipa_vr::streamer_read): New.
> 	(ipa_vr::streamer_write): New.
> 	(write_ipcp_transformation_info): Use new ipa_vr API.
> 	(read_ipcp_transformation_info): Same.
> 	(ipa_vr::nonzero_p): Delete.
> 	(ipcp_update_vr): Use new ipa_vr API.
> 	* ipa-prop.h (class ipa_vr): Provide an API and hide internals.
> 	* ipa-sra.cc (zap_useless_ipcp_results): Use new ipa_vr API.
> 	* gcc.dg/ipa/pr78121.c: Adjust for vrange::dump use.
> 	* gcc.dg/ipa/vrp1.c: Same.
> 	* gcc.dg/ipa/vrp2.c: Same.
> 	* gcc.dg/ipa/vrp3.c: Same.
> 	* gcc.dg/ipa/vrp4.c: Same.
> 	* gcc.dg/ipa/vrp5.c: Same.
> 	* gcc.dg/ipa/vrp6.c: Same.
> 	* gcc.dg/ipa/vrp7.c: Same.
> 	* gcc.dg/ipa/vrp8.c: Same.

      parent reply	other threads:[~2023-05-24 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 14:16 Aldy Hernandez
2023-05-22 18:42 ` Aldy Hernandez
2023-05-24 14:10 ` Martin Jambor [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=ri68rddddm6.fsf@suse.cz \
    --to=mjambor@suse.cz \
    --cc=aldyh@redhat.com \
    --cc=amacleod@redhat.com \
    --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).