Re: Allow more complex call replacements in gimple-fold.c

2015-10-26 Thread Richard Biener
On Mon, Oct 26, 2015 at 11:30 AM, Richard Sandiford wrote: > Richard Biener writes: >> On Mon, Oct 26, 2015 at 10:41 AM, Richard Sandiford >> wrote: >>> An upcoming patch adds a match.pd rule that folds pow(pow(x,y),z) >>> to pow(x,y*z). This fold can reuse the existing pow gimple statement >>>

Re: Allow more complex call replacements in gimple-fold.c

2015-10-26 Thread Richard Sandiford
Richard Biener writes: > On Mon, Oct 26, 2015 at 10:41 AM, Richard Sandiford > wrote: >> An upcoming patch adds a match.pd rule that folds pow(pow(x,y),z) >> to pow(x,y*z). This fold can reuse the existing pow gimple statement >> and simply replace the operands with x and y*z. However, the y*z

Re: Allow more complex call replacements in gimple-fold.c

2015-10-26 Thread Richard Biener
On Mon, Oct 26, 2015 at 10:41 AM, Richard Sandiford wrote: > An upcoming patch adds a match.pd rule that folds pow(pow(x,y),z) > to pow(x,y*z). This fold can reuse the existing pow gimple statement > and simply replace the operands with x and y*z. However, the y*z > itself requires a separate gi