Displaying 3 results from an estimated 3 matches for "cxxnamemangl".
Did you mean:
cxxnamemangler
2016 Dec 12
2
[RFC] Enable "#pragma omp declare simd" in the LoopVectorizer
...tor symbols look as follows:
>
> _ZVGQN2v__Z1fd
> _ZVGDN2v__Z1ff
> _ZVGQN4v__Z1ff
Hi Francesco,
The ARM AAPCS (A.2.1) says:
"For C++ the mangled name for parameters is as though the equivalent
type name was used."
Clang is already able to mangle NEON vectors of any length
(CXXNameMangler::mangleNeonVectorType), you should use that, as this
is very likely to be compatible with other compilers as well.
cheers,
--renato
2016 Dec 12
0
[RFC] Enable "#pragma omp declare simd" in the LoopVectorizer
On 12/12/2016 14:32, "Renato Golin" <renato.golin at linaro.org> wrote:
>Clang is already able to mangle NEON vectors of any length
>(CXXNameMangler::mangleNeonVectorType), you should use that, as this
>is very likely to be compatible with other compilers as well.
Hi Renato,
The “u”, “v”, “l” mangling of parameters has already been agreed
internally at ARM with the gcc team, and as Xinmin has pointed out, this
is going to guarantee compa...
2016 Dec 12
0
[RFC] Enable "#pragma omp declare simd" in the LoopVectorizer
Hi Xinmin,
I have updated the clang patch using the standard name mangling you
suggested - I was not fully aware of the C++ mangling convention “_ZVG”.
I am using “D” for 64-bit NEON and “Q” for 128-bit NEON, which makes NEON
vector symbols look as follows:
_ZVGQN2v__Z1fd
_ZVGDN2v__Z1ff
_ZVGQN4v__Z1ff
Here “Q” means -> NEON 128-bit, “D” means -> NEON 64-bit
Please notice that although