Displaying 3 results from an estimated 3 matches for "noalias_accesses".
2020 May 18
2
LLVM's loop unroller & llvm.loop.parallel_accesses
Would you guys be open to supporting a new hint with the right semantics,
like e.g. llvm.loop.noalias_accesses?! I would need to find support in
clang however and the main point of support would be the loop unroller
behaving as stated in the OP.
On Thu, May 14, 2020 at 3:04 PM Michael Kruse <llvmdev at meinersbur.de> wrote:
> Trivial example:
>
> #pragma clang loop vectorize(assume_safety)...
2020 May 19
2
LLVM's loop unroller & llvm.loop.parallel_accesses
...e its semantics? When would clang attach that attribute?
>
> Michael
>
> Am Mo., 18. Mai 2020 um 14:01 Uhr schrieb Hendrik Greving <
> hgreving at google.com>:
> >
> > Would you guys be open to supporting a new hint with the right
> semantics, like e.g. llvm.loop.noalias_accesses?! I would need to find
> support in clang however and the main point of support would be the loop
> unroller behaving as stated in the OP.
> >
> > On Thu, May 14, 2020 at 3:04 PM Michael Kruse <llvmdev at meinersbur.de>
> wrote:
> >>
> >> Trivial example...
2020 May 14
3
LLVM's loop unroller & llvm.loop.parallel_accesses
This is interesting! So are you saying that loop.parallel_accesses strictly
loop parallel, and says nothing about aliasing? I see, I guess we may
have been "abusing" the hint and re-purposed it. But isn't llvm's
vectorizer using loop.parallel_accesses to vectorize loops including
vectorize memory accesses that if you ignore loop-carried dependencies,
usually means effectively