Re: [PATCH 7/9] cprop: Leave RTX_FRAME_RELATED_P instructions alone

2016-09-09 Thread Segher Boessenkool
On Thu, Sep 08, 2016 at 11:55:04AM -0600, Jeff Law wrote: > On 07/31/2016 07:42 PM, Segher Boessenkool wrote: > >Doing cprop on frame-related instructions blows up spectacularly. > >So don't. > > > >2016-06-07 Segher Boessenkool > > > > * regcprop.c (copyprop_hardreg_forward_1): Don't change

Re: [PATCH 7/9] cprop: Leave RTX_FRAME_RELATED_P instructions alone

2016-09-08 Thread Jeff Law
On 07/31/2016 07:42 PM, Segher Boessenkool wrote: Doing cprop on frame-related instructions blows up spectacularly. So don't. 2016-06-07 Segher Boessenkool * regcprop.c (copyprop_hardreg_forward_1): Don't change RTX_FRAME_RELATED_P instructions. Example or testcase? jeff

[PATCH 7/9] cprop: Leave RTX_FRAME_RELATED_P instructions alone

2016-07-31 Thread Segher Boessenkool
Doing cprop on frame-related instructions blows up spectacularly. So don't. 2016-06-07 Segher Boessenkool * regcprop.c (copyprop_hardreg_forward_1): Don't change RTX_FRAME_RELATED_P instructions. --- gcc/regcprop.c | 4 1 file changed, 4 insertions(+) diff --git a/gcc/re

[PATCH 7/9] cprop: Leave RTX_FRAME_RELATED_P instructions alone

2016-06-07 Thread Segher Boessenkool
Doing cprop on frame-related instructions blows up spectacularly. So don't. 2016-06-07 Segher Boessenkool * regcprop.c (copyprop_hardreg_forward_1): Don't change RTX_FRAME_RELATED_P instructions. --- gcc/regcprop.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gcc/r