Re: [PATCH] combine: Update links correctly for new I2 (PR84169)

2018-02-14 Thread Jakub Jelinek
On Mon, Feb 12, 2018 at 03:59:05PM +, Segher Boessenkool wrote: > 2018-02-12 Segher Boessenkool > > PR rtl-optimization/84169 > * combine.c (try_combine): New variable split_i2i3. Set it to true if > we generated a parallel as new i3 and we split that to new i2 and i3 >

Re: [PATCH] combine: Update links correctly for new I2 (PR84169)

2018-02-13 Thread Segher Boessenkool
On Mon, Feb 12, 2018 at 05:12:20PM +0100, Jakub Jelinek wrote: > On Mon, Feb 12, 2018 at 03:59:05PM +, Segher Boessenkool wrote: > > If there is a LOG_LINK between two insns, this means those two insns > > can be combined, as far as dataflow is concerned. There never should > > be a LOG_LINK b

Re: [PATCH] combine: Update links correctly for new I2 (PR84169)

2018-02-12 Thread Jakub Jelinek
On Mon, Feb 12, 2018 at 03:59:05PM +, Segher Boessenkool wrote: > If there is a LOG_LINK between two insns, this means those two insns > can be combined, as far as dataflow is concerned. There never should > be a LOG_LINK between two unrelated insns. If there is one, combine > will try to com

Re: [PATCH] combine: Update links correctly for new I2 (PR84169)

2018-02-12 Thread Segher Boessenkool
On Mon, Feb 12, 2018 at 05:12:20PM +0100, Jakub Jelinek wrote: > On Mon, Feb 12, 2018 at 03:59:05PM +, Segher Boessenkool wrote: > > If there is a LOG_LINK between two insns, this means those two insns > > can be combined, as far as dataflow is concerned. There never should > > be a LOG_LINK b

[PATCH] combine: Update links correctly for new I2 (PR84169)

2018-02-12 Thread Segher Boessenkool
If there is a LOG_LINK between two insns, this means those two insns can be combined, as far as dataflow is concerned. There never should be a LOG_LINK between two unrelated insns. If there is one, combine will try to combine the insns without doing all the needed checks if the earlier destinatio