This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] See through ADDR_EXPR for forwprop
- From: Jeffrey A Law <law at redhat dot com>
- To: Richard Guenther <rguenth at tat dot physik dot uni-tuebingen dot de>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Thu, 26 May 2005 07:26:01 -0600
- Subject: Re: [PATCH] See through ADDR_EXPR for forwprop
- References: <4291C84C.6040201@tat.physik.uni-tuebingen.de>
- Reply-to: law at redhat dot com
On Mon, 2005-05-23 at 14:10 +0200, Richard Guenther wrote:
> This patch enables us to forward-propagate ADDR_EXPRs of the form
>
> alias2.cpp.t21.dce1:
> D.2326_109 = &dX.D.2303.D.2259.domain_m[0].D.2216;
> D.2326_110 = D.2326_109;
> D.2327_111 = &D.2326_110->D.2207;
> this_112 = D.2327_111;
> D.2802_113 = this_112->D.2161.domain_m;
>
> alias2.cpp.t22.forwprop1
> D.2802_113 = dX.D.2303.D.2259.domain_m[0].D.2216.D.2207.D.2161.domain_m;
>
> in one step, instead of waiting for .t75.forwprop3 like
> happened in the testcase for PR19626.
>
> Any reason why we should not do this?
>
> Bootstrapped on x86_64-unknown-linux-gnu, regtesting in progress.
>
> Ok for mainline after slush?
>
> Thanks,
> Richard.
> plain text document attachment (fix-forwprop)
> 2005-05-23 Richard Guenther <rguenth@gcc.gnu.org>
>
> * tree-ssa-forwprop.c (forward_propagate_addr_expr):
> See through ADDR_EXPR in finding place to propagate into.
I'm pretty sure you can't have an ADDR_EXPR on the LHS, so I suspect
checking for it is just a tiny waste of time. I'm going to rebootstrap
and retest with the first hunk removed.
jeff