search for: notinbranch

...ion variant that is a base language identifier, or, for C++, a template-id. <simd clauses> := <simdlen>, <mask>{, <optional simd clauses>} <simdlen> := simdlen(<positive number>) | simdlen("scalable") <mask> := inbranch | notinbranch <optional simd clauses> := <linear clause> | <uniform clause> | <align clause> | {,<optional simd clauses>} <linear clause> := linear_ref(<var>,<step>) | linear_var(<var>,...

...ge identifier, or, > for C++, a template-id. > > <simd clauses> := <simdlen>, <mask>{, <optional simd clauses>} > > <simdlen> := simdlen(<positive number>) | simdlen("scalable") > > <mask> := inbranch | notinbranch > > <optional simd clauses> := <linear clause> > | <uniform clause> > | <align clause> | {,<optional simd clauses>} > > <linear clause> := linear_ref(<var>,<step>) >...

...a template-id. >> > >> > <simd clauses> := <simdlen>, <mask>{, <optional simd clauses>} >> > >> > <simdlen> := simdlen(<positive number>) | simdlen("scalable") >> > >> > <mask> := inbranch | notinbranch >> > >> > <optional simd clauses> := <linear clause> >> > | <uniform clause> >> > | <align clause> | {,<optional simd clauses>} >> > >> > <linear clause> :...

...for C++, a template-id. > > > > <simd clauses> := <simdlen>, <mask>{, <optional simd clauses>} > > > > <simdlen> := simdlen(<positive number>) | simdlen("scalable") > > > > <mask> := inbranch | notinbranch > > > > <optional simd clauses> := <linear clause> > > | <uniform clause> > > | <align clause> | {,<optional simd > > clauses>} > > > > <linear clause> := linear_ref(...

...st scalable (i.e. vector-length agnostic) functions for SVE. > > This would definitely look like implementing `declare variant`, as the attribute would need to accept something like the following: > > ``` > . . . __attribute__(simd_variant(“vector_version”,“context={simd(simdlen(2),notinbranch”},device={isa(“simd")})) > ``` > > Using the sub-string from the mangled name to me has the following advantages: > > 1. No need to deal with `declare variant`. > 2. [...] > 3. In terms of usability, there is no need to reinvent the wheel. The > `declare variant` of...

...for C++, a template-id. > > > > <simd clauses> := <simdlen>, <mask>{, <optional simd clauses>} > > > > <simdlen> := simdlen(<positive number>) | simdlen("scalable") > > > > <mask> := inbranch | notinbranch > > > > <optional simd clauses> := <linear clause> > > | <uniform clause> > > | <align clause> | {,<optional simd > > clauses>} > > > > <linear clause> := linear_ref(&...

>Thank you everybody for their input, and for your patience. This is proving harder than expected! :) Thank you for doing the hard part of the work. Hideki -----Original Message----- From: Francesco Petrogalli [mailto:Francesco.Petrogalli at arm.com] Sent: Monday, June 24, 2019 11:26 AM To: Saito, Hideki <hideki.saito at intel.com> Cc: Doerfert, Johannes <jdoerfert at anl.gov>;

Hi all, I am submitting the following RFC [1] to re-implement -fveclib via OpenMP constructs. The RFC was discussed during a round table at the last LLVM developer meeting, and presented during the BoF [2]. The proposal is published on Phabricator, for the purpose of keeping track of the comments, and it now ready for a review from a wider audience after being polished by Hal Finkel and Hideki

...x double>(2 x double>). > > The problem with this choice is the number of vector version available for a target is not unique. > > In particular, the following declaration generates multiple vector versions, depending on the target: > > #pragma omp declare simd simdlen(2) notinbranch > double foo(double) {…}; > > On x86, this generates at least 4 symbols (one for SSE, one for AVX, one for AVX2, and one for AVX512: https://godbolt.org/z/TLYXPi) > > On aarch64, the same declaration generates a unique symbol, as specified in the Vector Function ABI. > > Thi...

...>> The problem with this choice is the number of vector version available for a target is not unique. >>> >>> In particular, the following declaration generates multiple vector versions, depending on the target: >>> >>> #pragma omp declare simd simdlen(2) notinbranch >>> double foo(double) {…}; >>> >>> On x86, this generates at least 4 symbols (one for SSE, one for AVX, one for AVX2, and one for AVX512: https://godbolt.org/z/TLYXPi) >>> >>> On aarch64, the same declaration generates a unique symbol, as specified in...

...t;>>> correspondent `#pragma omp declare variant` defined in OpenMP 5.0, as in >>>>>> the following example. >>>>>> >>>>>> #pragma clang declare variant(vector_sinf) \ >>>>>> match(construct=simd(simdlen(4),notinbranch), device={isa("simd")}) >>>>>> extern float sinf(float); >>>>>> >>>>>> float32x4_t vector_sinf(float32x4_t x); >>>>>> >>>>>> The `construct` set in the directive, together with the `devic...

...hoice is the number of vector version available for a target is not unique. >>>>> >>>>> In particular, the following declaration generates multiple vector versions, depending on the target: >>>>> >>>>> #pragma omp declare simd simdlen(2) notinbranch >>>>> double foo(double) {…}; >>>>> >>>>> On x86, this generates at least 4 symbols (one for SSE, one for AVX, one for AVX2, and one for AVX512: https://godbolt.org/z/TLYXPi) >>>>> >>>>> On aarch64, the same declaration ge...

...rsion available for a target is not unique. >>>>>>> >>>>>>> In particular, the following declaration generates multiple vector versions, depending on the target: >>>>>>> >>>>>>> #pragma omp declare simd simdlen(2) notinbranch >>>>>>> double foo(double) {…}; >>>>>>> >>>>>>> On x86, this generates at least 4 symbols (one for SSE, one for AVX, one for AVX2, and one for AVX512: https://godbolt.org/z/TLYXPi) >>>>>>> >>>>>>...

...the number of vector version available > for a target is not unique. For me, this simply means this mangling scheme is not sufficient. > In particular, the following declaration generates multiple vector > versions, depending on the target: > > #pragma omp declare simd simdlen(2) notinbranch > double foo(double) {…}; > > On x86, this generates at least 4 symbols (one for SSE, one for AVX, > one for AVX2, and one for AVX512: https://godbolt.org/z/TLYXPi) > > On aarch64, the same declaration generates a unique symbol, as > specified in the Vector Function ABI. I f...

...t; `#pragma clang declare variant` according to the rule defined by the >> correspondent `#pragma omp declare variant` defined in OpenMP 5.0, as in >> the following example. >> >> #pragma clang declare variant(vector_sinf) \ >> match(construct=simd(simdlen(4),notinbranch), device={isa("simd")}) >> extern float sinf(float); >> >> float32x4_t vector_sinf(float32x4_t x); >> >> The `construct` set in the directive, together with the `device` set, is >> used to generate the vector mangled name to be used in the &gt...

...different from declaring these N variants explicitly with the respective declare variant match clause. > >> In particular, the following declaration generates multiple vector > >> versions, depending on the target: > >> > >> #pragma omp declare simd simdlen(2) notinbranch > >> double foo(double) {…}; > >> > >> On x86, this generates at least 4 symbols (one for SSE, one for AVX, > >> one for AVX2, and one for AVX512: https://godbolt.org/z/TLYXPi) > >> > >> On aarch64, the same declaration generates a unique symb...

...ng to the rule defined by the >>>> correspondent `#pragma omp declare variant` defined in OpenMP 5.0, as in >>>> the following example. >>>> >>>> #pragma clang declare variant(vector_sinf) \ >>>> match(construct=simd(simdlen(4),notinbranch), device={isa("simd")}) >>>> extern float sinf(float); >>>> >>>> float32x4_t vector_sinf(float32x4_t x); >>>> >>>> The `construct` set in the directive, together with the `device` set, is >>>> used to gene...

...N variants explicitly with the respective declare variant match clause. > > > > >> In particular, the following declaration generates multiple vector > > >> versions, depending on the target: > > >> > > >> #pragma omp declare simd simdlen(2) notinbranch double foo(double) > > >> {…}; > > >> > > >> On x86, this generates at least 4 symbols (one for SSE, one for > > >> AVX, one for AVX2, and one for AVX512: > > >> https://godbolt.org/z/TLYXPi) > > >> > > >> On a...

...re simd is not target independent. Your expectation are met only inside one target. > >>>> In particular, the following declaration generates multiple vector >>>> versions, depending on the target: >>>> >>>> #pragma omp declare simd simdlen(2) notinbranch double foo(double) >>>> {…}; >>>> >>>> On x86, this generates at least 4 symbols (one for SSE, one for >>>> AVX, one for AVX2, and one for AVX512: >>>> https://godbolt.org/z/TLYXPi) >>>> >>>> On aarch64, the sa...

...Your expectation are met only inside one target. > > > > > >>>> In particular, the following declaration generates multiple > >>>> vector versions, depending on the target: > >>>> > >>>> #pragma omp declare simd simdlen(2) notinbranch double > >>>> foo(double) {…}; > >>>> > >>>> On x86, this generates at least 4 symbols (one for SSE, one for > >>>> AVX, one for AVX2, and one for AVX512: > >>>> https://godbolt.org/z/TLYXPi) > >>>> > &g...