This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch] OPT: Update heuristics for loop-invariant for address arithmetic.
- From: Vladimir Makarov <vmakarov at redhat dot com>
- To: Ajit Kumar Agarwal <ajit dot kumar dot agarwal at xilinx dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Cc: Vinod Kathail <vinodk at xilinx dot com>, Shail Aditya Gupta <shailadi at xilinx dot com>, Vidhumouli Hunsigida <vidhum at xilinx dot com>, Nagaraju Mekala <nmekala at xilinx dot com>
- Date: Mon, 23 Mar 2015 17:58:41 -0400
- Subject: Re: [Patch] OPT: Update heuristics for loop-invariant for address arithmetic.
- Authentication-results: sourceware.org; auth=none
- References: <d3236939cb3e4429881fed98dbc192fe at BN1AFFO11FD054 dot protection dot gbl> <BN1AFFO11FD00800EA27D828C1EE45E868AE0D0 at BN1AFFO11FD008 dot protection dot gbl>
On 2015-03-23 12:35 PM, Ajit Kumar Agarwal wrote:
> Hello All:
>
> Did you get a chance to look at the below patch.
>
> Thanks & Regards
> Ajit
>
> -----Original Message-----
> From: gcc-patches-owner@gcc.gnu.org [mailto:gcc-patches-owner@gcc.gnu.org] On Behalf Of Ajit Kumar Agarwal
> Sent: Wednesday, March 04, 2015 3:57 PM
> To: vmakarov@redhat.com; GCC Patches
> Cc: Vinod Kathail; Shail Aditya Gupta; Vidhumouli Hunsigida; Nagaraju Mekala
> Subject: [Patch] OPT: Update heuristics for loop-invariant for address arithmetic.
>
> Hello All:
>
> The changes are made in the patch to update the heuristics for loop invariant for address arithemetic at RTL Level.
> The heuristics are updated with the consideration of single def and use for register pressure calculation instead Of ignoring it and also to update the estimated register pressure cost along with the check of actual uses with Address uses.
>
> With the above change, gains are seen in the Geomean for Mibench/EEMBC benchmarks for microblaze target. No Regression is seen in deja GNU regressions tests for microblaze.
>
>
Sorry, I am not a maintainer/reviewer of loop invariant motion pass.
I had no power to approve this, especially when you change mostly code
for ! flag_ira_loop_pressure.
I only should say that microblaze is not a primary target. You should
demonstrate improvement on a primary target, x86/x86-64 the best.
SPEC2000 or SPEC2006 would be a good benchmark for this.