Re: [Patch, tentative] Use MOVE_MAX_PIECES instead of MOVE_MAX in gimple_fold_builtin_memory_op

2016-11-28 Thread Jeff Law
On 11/25/2016 01:04 AM, Richard Biener wrote: On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote: Richard Biener writes: On Thu, 24 Nov 2016, Richard Biener wrote: On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote: Hi, I've been analyzing a failing regtest (gcc.dg/strlenopt-8.c) for

Re: [Patch, tentative] Use MOVE_MAX_PIECES instead of MOVE_MAX in gimple_fold_builtin_memory_op

2016-11-25 Thread Richard Biener
On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote: > > Richard Biener writes: > > > On Thu, 24 Nov 2016, Richard Biener wrote: > > > >> On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote: > >> > >> > Hi, > >> > > >> > I've been analyzing a failing regtest (gcc.dg/strlenopt-8.c) for the > >>

Re: [Patch, tentative] Use MOVE_MAX_PIECES instead of MOVE_MAX in gimple_fold_builtin_memory_op

2016-11-24 Thread Senthil Kumar Selvaraj
Richard Biener writes: > On Thu, 24 Nov 2016, Richard Biener wrote: > >> On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote: >> >> > Hi, >> > >> > I've been analyzing a failing regtest (gcc.dg/strlenopt-8.c) for the avr >> > target. I found that the (dump) failure is because there are 4 >>

Re: [Patch, tentative] Use MOVE_MAX_PIECES instead of MOVE_MAX in gimple_fold_builtin_memory_op

2016-11-24 Thread Richard Biener
On Thu, 24 Nov 2016, Richard Biener wrote: > On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote: > > > Hi, > > > > I've been analyzing a failing regtest (gcc.dg/strlenopt-8.c) for the avr > > target. I found that the (dump) failure is because there are 4 > > instances of memcpy, while the

Re: [Patch, tentative] Use MOVE_MAX_PIECES instead of MOVE_MAX in gimple_fold_builtin_memory_op

2016-11-24 Thread Richard Biener
On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote: > Hi, > > I've been analyzing a failing regtest (gcc.dg/strlenopt-8.c) for the avr > target. I found that the (dump) failure is because there are 4 > instances of memcpy, while the testcase expects only 2 for a > non-strict align target

[Patch, tentative] Use MOVE_MAX_PIECES instead of MOVE_MAX in gimple_fold_builtin_memory_op

2016-11-24 Thread Senthil Kumar Selvaraj
Hi, I've been analyzing a failing regtest (gcc.dg/strlenopt-8.c) for the avr target. I found that the (dump) failure is because there are 4 instances of memcpy, while the testcase expects only 2 for a non-strict align target like the avr. Comparing that with a dump generated by