Displaying 6 results from an estimated 6 matches for "addreductionvar".
2013 Oct 21
5
[LLVMdev] First attempt at recognizing pointer reduction
Hi Nadav, Arnold,
I managed to find some time to work on the pointer reduction, and I got a
patch that can make "canVectorize()" pass.
Basically what I do is to teach AddReductionVar() about pointers, saying
they don't really have an exit instructions, and that (maybe) the final
store is a good candidate (is it?).
This makes it recognize the writes and reads, but then
"canVectorizeMemory()" bails because it can't find the array bounds. This
will be my next st...
2013 Oct 21
0
[LLVMdev] First attempt at recognizing pointer reduction
...s,
Nadav
On Oct 21, 2013, at 8:23 AM, Renato Golin <renato.golin at linaro.org> wrote:
> Hi Nadav, Arnold,
>
> I managed to find some time to work on the pointer reduction, and I got a patch that can make "canVectorize()" pass.
>
> Basically what I do is to teach AddReductionVar() about pointers, saying they don't really have an exit instructions, and that (maybe) the final store is a good candidate (is it?).
>
> This makes it recognize the writes and reads, but then "canVectorizeMemory()" bails because it can't find the array bounds. This will be...
2016 May 20
0
Working on FP SCEV Analysis
...is an add-recurrence that was detected by SCEV. The idea is to add a fall-back to analyze the PHI directly if its type is a float.
There is already precedence for such things in LV. We support more reductions (including floating-point) than what SCEV can analyze, therefore RecurrenceDescriptor::AddReductionVar needs to analyze PHIs directly.
Adam
>
> Thanks,
> Hideki
>
> ----------------------
> I looked at what our FORTRAN compiler (non-LLVM) does for the following (x, y, z, and f are float by default typing,
> based on names).
>
> subroutine foo(x, y, z, A, N)...
2016 May 24
1
Working on FP SCEV Analysis
...at was detected by SCEV. The idea is to add a fall-back to
> analyze the PHI directly if its type is a float.
>
> There is already precedence for such things in LV. We support more
> reductions (including floating-point) than what SCEV can analyze, therefore
> RecurrenceDescriptor::AddReductionVar needs to analyze PHIs directly.
>
> Adam
>
>
> Thanks,
> Hideki
>
> ----------------------
> I looked at what our FORTRAN compiler (non-LLVM) does for the following (x,
> y, z, and f are float by default typing,
> based on names).
>
> subroutine foo(x,...
2013 Oct 21
0
[LLVMdev] First attempt at recognizing pointer reduction
...Arnold
On Oct 21, 2013, at 10:23 AM, Renato Golin <renato.golin at linaro.org> wrote:
> Hi Nadav, Arnold,
>
> I managed to find some time to work on the pointer reduction, and I got a patch that can make "canVectorize()" pass.
>
> Basically what I do is to teach AddReductionVar() about pointers, saying they don't really have an exit instructions, and that (maybe) the final store is a good candidate (is it?).
>
> This makes it recognize the writes and reads, but then "canVectorizeMemory()" bails because it can't find the array bounds. This will be...
2016 May 20
5
Working on FP SCEV Analysis
To the best of my experience, handling case B (secondary induction) is must-have, and if I’m not mistaken,
people aren’t opposed to that.
For me, handling case A (primary induction) is “why not?”, but I certainly admit that that can be very naïve
thinking coming from lack of good understanding on SCEV and their proper usages. Now, let’s assume we
can postpone discussion about case A. What is the