Re: portability of __m128i static initializers between gcc and Microsoft C

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Apr 24, 2009 at 6:51 PM, Tim Prince <TimothyPrince@xxxxxxxxxxxxx> wrote:
> Ian Lance Taylor wrote:
>> "Blower, Melanie" <melanie.blower@xxxxxxxxx> writes:
>>
>>> I discovered an incompatability of the type definition of __m128i
>>> between gcc and Microsoft C that may cause a problem when moving
>>> source code between these two compilers when static initializers are
>>> used. Is there a process to address discrepancies of this nature?
>>
>> The __m128i type is specified by Intel.  So if gcc differs from icc, we
>> should change it.
>>

__m128i is only specified as 128bit integer vector. Constant initializer is
unspecified. The only portable way to initialize a vector is to use
_mm_set_XXX intrinsics.



-- 
H.J.


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux