From: Richard Biener <rguenther@suse.de>
To: Jiong Wang <jiong.wang@foss.arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch] PR tree-optimization/68234 Improve range info for loop Phi node
Date: Wed, 11 Nov 2015 10:26:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.11.1511111126000.4884@t29.fhfr.qr> (raw)
In-Reply-To: <5643091B.9090009@foss.arm.com>
On Wed, 11 Nov 2015, Jiong Wang wrote:
> As discussed at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68234, this
> patch haven't touch the existed code logic in vrp_visit_phi_node, it
> only entends SCEV check to those VR_VARYING loop PHI node.
>
> Previously, we only do this check if the PHI node is with valid range
> info but later dropped either side to infinite. The miss of those PHI
> node with initial estimiation of VR_VARYING caused the missing of some
> further optimization opportunity, for example the testcase included in
> this patch, with improved range info, we can efficient turn the signed
> divide into right shift.
>
> This patch pass x86-64 and AArch64 boostrap, no regression on both.
> Meanwhile a simple benchmaring shows there are quite a few new VR_RANGE
> found after this patch during gcc bootstrapping. There is no performance
> regression on spec2006 int on aarch64.
>
> During gcc bootstrapping, on x86-64 there are 4828 new VR_VARYING -> VR_RANGE
> found by vrp1, and 5008 new by vrp2.
>
> While on AArch64 there are 44756 new by vrp1, and 6047 new by vrp2.
>
> OK for trunk?
Ok.
Thanks,
Richard.
> 2015-11-11 Richard Biener <rguenth@gcc.gnu.org>
> Jiong Wang <jiong.wang@arm.com>
> gcc/
> PR tree-optimization/68234
> * tree-vrp.c (vrp_visit_phi_node): Extend SCEV check to those loop PHI
> node which estimiated to be VR_VARYING initially.
>
> gcc/testsuite/
> * gcc.dg/tree-ssa/pr68234.c: New testcase.
prev parent reply other threads:[~2015-11-11 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 9:23 Jiong Wang
2015-11-11 10:26 ` Richard Biener [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=alpine.LSU.2.11.1511111126000.4884@t29.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiong.wang@foss.arm.com \
/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).