You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1649 | /// Loads a 64-bit integer value to the low element of a 128-bit integer
1650 | /// vector and clears the upper element.
1651 | ///
1652 | /// \headerfile <x86intrin.h>
1653 | ///
1654 | /// This intrinsic corresponds to the <c> VMOVQ / MOVQ </c> instruction.
1655 | ///
1656 | /// \param __a
1657 | /// A pointer to a 64-bit memory location. The address of the memory
1658 | /// location does not have to be aligned.
1659 | /// \returns A 128-bit vector of [2 x i64] containing the loaded value.
1660 | static __inline__ __m128i __DEFAULT_FN_ATTRS
1661 | _mm_loadu_si64(void const *__a)
1662 | {
1663 | struct __loadu_si64 {
1664 | long long __v;
1665 | } __attribute__((__packed__, __may_alias__));
1666 | long long __u = ((const struct __loadu_si64*)__a)->__v;
1667 | return __extension__ (__m128i)(__v2di){__u, 0LL};
1668 | }
clang-scan complains about 1666 in particular.
Future work: take a look at their bug tracker to see if this is a known bug in clang-scan.
The text was updated successfully, but these errors were encountered:
clang-scan 13.0.0 complaints about
in
cpusupport/Build/cpusupport-X86-AESNI.c
.Clang's <emmintrin.h> header looks ok to me:
clang-scan complains about 1666 in particular.
Future work: take a look at their bug tracker to see if this is a known bug in clang-scan.
The text was updated successfully, but these errors were encountered: