On Mon, Jun 1, 2015 at 4:00 PM, Richard Biener
wrote:
> On Sat, May 30, 2015 at 7:47 AM, Jeff Law wrote:
>> On 05/19/2015 10:12 AM, Aditya K wrote:
>>>
>>> w.r.t. the PR48052, here is the patch which finds out if scev would wrap
>>> or not.
>>> The patch symbolically evaluates if valid_niter>= lo
On Sat, May 30, 2015 at 7:47 AM, Jeff Law wrote:
> On 05/19/2015 10:12 AM, Aditya K wrote:
>>
>> w.r.t. the PR48052, here is the patch which finds out if scev would wrap
>> or not.
>> The patch symbolically evaluates if valid_niter>= loop->nb_iterations is
>> true. In that case the scev would not
On 05/19/2015 10:12 AM, Aditya K wrote:
w.r.t. the PR48052, here is the patch which finds out if scev would wrap or not.
The patch symbolically evaluates if valid_niter>= loop->nb_iterations is true.
In that case the scev would not wrap (??).
Currently, we only look for two special 'patterns', w
@gmail.com;
> l...@redhat.com; richard.guent...@gmail.com
> Subject: Fix PR48052: loop not vectorized if index is "unsigned int"
> Date: Tue, 19 May 2015 16:12:26 +
>
> w.r.t. the PR48052, here is the patch which finds out if scev would wrap or
> not.
> The patch
w.r.t. the PR48052, here is the patch which finds out if scev would wrap or not.
The patch symbolically evaluates if valid_niter>= loop->nb_iterations is true.
In that case the scev would not wrap (??).
Currently, we only look for two special 'patterns', which are sufficient to
analyze the simple
On Wed, May 6, 2015 at 7:02 PM, Richard Biener
wrote:
> On Mon, May 4, 2015 at 9:47 PM, Abderrazek Zaafrani
> wrote:
>> This is an old thread and we are still running into similar issues:
>> Code is not being vectorized on 64-bit target due to scev not being
>> able to optimally analyze overflow
Richard,
Agree that the code is handling a very special case but this special
case is common enough and is limiting the vectorizer in a significant
way. The special case is: loops with unsigned index, non-constant
start value, and step 1. We have a code for a matrix multiply – loops
blocked by han
On Mon, May 4, 2015 at 9:47 PM, Abderrazek Zaafrani
wrote:
> This is an old thread and we are still running into similar issues:
> Code is not being vectorized on 64-bit target due to scev not being
> able to optimally analyze overflow condition.
>
> While the original test case shown here seems t
This is an old thread and we are still running into similar issues:
Code is not being vectorized on 64-bit target due to scev not being
able to optimally analyze overflow condition.
While the original test case shown here seems to work now, it does not
work if the start value is not a constant and
