This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Should we update __builtin_ia32_palignr?
- From: Uros Bizjak <ubizjak at gmail dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: GCC <gcc at gcc dot gnu dot org>
- Date: Thu, 01 May 2008 10:40:36 +0200
- Subject: Re: Should we update __builtin_ia32_palignr?
- References: <6dc9ffc80804301540h2fe1cd21v212af2b514f6d351@mail.gmail.com>
H.J. Lu wrote:
We currently define __builtin_ia32_palignr as
long long __builtin_ia32_palignr (long long, long long, int)
But it really should be
v1di __builtin_ia32_palignr (v1di, v1di, int)
Fix it won't affect sources which use intrinsics defined
in tmmintrin.h. But it may affect codes which use
__builtin_ia32_palignr directly. But I don't think there
are many users who use MMX version of gcc SSSE3
builtins directly. Should I submit a patch to change it?
Builtins are considered as internal gcc infrastructure, so they can be
changed at will as long as published interface (intrinsics in header
files) are kept the same.
Uros.