Displaying 4 results from an estimated 4 matches for "__simd64".
Did you mean:
__amd64
2010 Sep 22
2
[LLVMdev] Vectors in structures
...ment doesn't require you to meet it in any
particular way as long as you end up with the right strings.
I.e. the mangling requirement places no requirements at all on
the implementation, outside of mangled names.
The controversial statement is where A.2 requires the user types to
map on to the __simd64 structures. But that still isn't an argument
for wrapping. This sentence might be significant:
"The structures have 64-bit alignment and map directly onto the
containerized vector fundamental data types."
So the structures map _directly_ on to the vector types - not on to
wrappers...
2010 Sep 22
0
[LLVMdev] Vectors in structures
...o meet it in any
> particular way as long as you end up with the right strings.
> I.e. the mangling requirement places no requirements at all on
> the implementation, outside of mangled names.
>
> The controversial statement is where A.2 requires the user types to
> map on to the __simd64 structures. But that still isn't an argument
> for wrapping. This sentence might be significant:
>
> "The structures have 64-bit alignment and map directly onto the
> containerized vector fundamental data types."
>
> So the structures map _directly_ on to the vec...
2010 Sep 21
0
[LLVMdev] Vectors in structures
...ector types" which I guess could be read
> as saying they are packed inside structures - but I don't think this
> is the intention and it doesn't match implementations.
> The arm_neon.h implementation in the ARM compiler defines the user
> types in terms of C structs called __simd64_int8_t etc. and the
> mangling originated as an artifact of this. But the C structs aren't
> wrapped vectors; they wrap double or a pair of doubles, to get the
> size and alignment. Their only purpose is to be recognized by name
> by the front end and turned into a native register...
2010 Sep 21
3
[LLVMdev] Vectors in structures
...describe the short vector types" which I guess could be read
as saying they are packed inside structures - but I don't think this
is the intention and it doesn't match implementations.
The arm_neon.h implementation in the ARM compiler defines the user
types in terms of C structs called __simd64_int8_t etc. and the
mangling originated as an artifact of this. But the C structs aren't
wrapped vectors; they wrap double or a pair of doubles, to get the
size and alignment. Their only purpose is to be recognized by name
by the front end and turned into a native register type.
In gcc's...