Displaying 3 results from an estimated 3 matches for "_zgvbn4ul_".
2016 Mar 02
4
Proposal for function vectorization and loop vectorization with function calls
...nts to be generated by the back-end. E.g.,
#pragma omp delcare simd uniform(a) linear(k)
float dowork(float *a, int k)
{
a[k] = sinf(a[k]) + 9.8f;
}
define __stdcall f32 @_dowork(f32* %a, i32 %k) #0
... ...
attributes #0 = { nounwind uwtable "_ZGVbM4ul_" "_ZGVbN4ul_" ...}
2. A new vector function generation pass is introduced to generate vector
variants of the original scalar function based on VectorABI (see [2, 3]).
For example, one vector variant is generated for "_ZGVbN4ul_" attribute
as follows (pseudo code):
define __stdcall &...
2016 Mar 02
2
Proposal for function vectorization and loop vectorization with function calls
...>
> #pragma omp delcare simd uniform(a) linear(k)
> float dowork(float *a, int k)
> {
> a[k] = sinf(a[k]) + 9.8f;
> }
>
> define __stdcall f32 @_dowork(f32* %a, i32 %k) #0
> ... ...
> attributes #0 = { nounwind uwtable "_ZGVbM4ul_" "_ZGVbN4ul_" ...}
>
> 2. A new vector function generation pass is introduced to generate vector
> variants of the original scalar function based on VectorABI (see [2, 3]).
> For example, one vector variant is generated for "_ZGVbN4ul_" attribute
> as follows (pseudo code):...
2016 Mar 02
5
RFC: Implementing the Swift calling convention in LLVM and Clang
> On Mar 2, 2016, at 1:33 AM, Renato Golin <renato.golin at linaro.org> wrote:
>
> On 2 March 2016 at 01:14, John McCall via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> Hi, all.
>> - We sometimes want to return more values in registers than the convention normally does, and we want to be able to use both integer and floating-point registers. For