Displaying 3 results from an estimated 3 matches for "scalarname".
Did you mean:
scalar3same
2016 Nov 30
5
[RFC] Enable "#pragma omp declare simd" in the LoopVectorizer
Dear all,
I have just created a couple of differential reviews to enable the
vectorisation of loops that have function calls to routines marked with
“#pragma omp declare simd”.
They can be (re)viewed here:
* https://reviews.llvm.org/D27249
* https://reviews.llvm.org/D27250
The current implementation allows the loop vectorizer to generate vector
code for source file as:
#pragma omp declare
2016 Dec 08
6
[RFC] Enable "#pragma omp declare simd" in the LoopVectorizer
...st famous words?).
### Step 3
This step happens in the LoopVectorizer. The InnerLoopVectorizer queries the TargetLibraryInfo looking for a vectorized version of the function by scalar name and function signature with the following method:
TargetLibraryInfo::isFunctionVectorizable(std::string ScalarName, FuncionType *FTy);
This is done in a way similar to what my current llvm patch does: the loop vectorizer makes up the function signature it needs and look for it in the TLI. If a match is found, vectorization is possible. Right now the compiler is not aware of uniform/linear function attributes,...
2016 Dec 12
0
[RFC] Enable "#pragma omp declare simd" in the LoopVectorizer
...Step 3
>
>This step happens in the LoopVectorizer. The InnerLoopVectorizer queries
>the TargetLibraryInfo looking for a vectorized version of the function by
>scalar name and function signature with the following method:
>
> TargetLibraryInfo::isFunctionVectorizable(std::string ScalarName,
>FuncionType *FTy);
>
>This is done in a way similar to what my current llvm patch does: the
>loop vectorizer makes up the function signature it needs and look for it
>in the TLI. If a match is found, vectorization is possible. Right now the
>compiler is not aware of uniform/line...