Displaying 2 results from an estimated 2 matches for "noalias_acccesses".
Did you mean:
noalias_accesses
2020 May 19
2
LLVM's loop unroller & llvm.loop.parallel_accesses
...lias semantics, e.g.
loop parallel semantics are sufficient. What's missing is a way to express
that past the llvm unroller. When the unroller merges iterations, loop
parallel no longer depicts the original iterations. So the obvious idea was
using noalias scope metadata for this, and llvm.loop.noalias_acccesses
would cause the unroller to propagate different scopes for each iteration.
Thinkable is also to keep the llvm.loop.parallel_accesses, and the unroller
propagates a new type of metadata analog to noalias scope, but
loop_parallel scope or something like that. We have methods to achieve this
with intr...
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