Re: [PATCH] Use get_range_info in vect_recog_divmod_pattern

2013-10-23 Thread Richard Biener
On Wed, 23 Oct 2013, Jakub Jelinek wrote: > On Wed, Oct 23, 2013 at 11:14:54AM +0200, Richard Biener wrote: > > On Tue, 22 Oct 2013, Jakub Jelinek wrote: > > > > > Hi! > > > > > > If VRP tells us that oprnd is always >= 0 or always < 0, we can generate > > > better code for the divmode vectoriza

Re: [PATCH] Use get_range_info in vect_recog_divmod_pattern

2013-10-23 Thread Jakub Jelinek
On Wed, Oct 23, 2013 at 11:14:54AM +0200, Richard Biener wrote: > On Tue, 22 Oct 2013, Jakub Jelinek wrote: > > > Hi! > > > > If VRP tells us that oprnd is always >= 0 or always < 0, we can generate > > better code for the divmode vectorization. > > > > Bootstrapped/regtested on x86_64-linux and

Re: [PATCH] Use get_range_info in vect_recog_divmod_pattern

2013-10-23 Thread Richard Biener
On Tue, 22 Oct 2013, Jakub Jelinek wrote: > Hi! > > If VRP tells us that oprnd is always >= 0 or always < 0, we can generate > better code for the divmode vectorization. > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? Testcase...? Ok with adding one (I suggest a x86 sp

[PATCH] Use get_range_info in vect_recog_divmod_pattern

2013-10-22 Thread Jakub Jelinek
Hi! If VRP tells us that oprnd is always >= 0 or always < 0, we can generate better code for the divmode vectorization. Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2013-10-22 Jakub Jelinek * tree-vect-patterns.c (vect_recog_divmod_pattern): Optimize s