Re: Silecne array bounds warnings in duplicated code

2012-10-12 Thread Jan Hubicka
> On Fri, 12 Oct 2012, Jan Hubicka wrote: > > > > On Thu, 11 Oct 2012, Jan Hubicka wrote: > > > > > > > Hi, > > > > this patch address problem I run into with strenghtened cunroll pass. > > > > I made > > > > cunroll to use loop_max_iterations bounds into an account that makes us > > > > to >

Re: Silecne array bounds warnings in duplicated code

2012-10-12 Thread Richard Biener
On Fri, 12 Oct 2012, Jan Hubicka wrote: > > On Thu, 11 Oct 2012, Jan Hubicka wrote: > > > > > Hi, > > > this patch address problem I run into with strenghtened cunroll pass. I > > > made > > > cunroll to use loop_max_iterations bounds into an account that makes us to > > > occasionally produce

Re: Silecne array bounds warnings in duplicated code

2012-10-12 Thread Jan Hubicka
> On Thu, 11 Oct 2012, Jan Hubicka wrote: > > > Hi, > > this patch address problem I run into with strenghtened cunroll pass. I > > made > > cunroll to use loop_max_iterations bounds into an account that makes us to > > occasionally produce out of bounds loop accesses in loop like: > > > > for

Re: Silecne array bounds warnings in duplicated code

2012-10-11 Thread Richard Biener
On Thu, 11 Oct 2012, Jan Hubicka wrote: > Hi, > this patch address problem I run into with strenghtened cunroll pass. I made > cunroll to use loop_max_iterations bounds into an account that makes us to > occasionally produce out of bounds loop accesses in loop like: > > for (i=0;i { > > if