https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91342
--- Comment #2 from Alex Yee ---
Oh I didn't realize Intel's docs were conflicting. I think most people just use
the interactive intrinsics guide.
MSVC and Intel's own compiler implement the void* variants. Thus, this comes up
when porting code
y: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: a-yee at u dot northwestern.edu
Target Milestone: ---
Potentially Related:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91344
The following code compiles on Clang, MSVC, and ICC. But it fails on GCC.
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: a-yee at u dot northwestern.edu
Target Milestone: ---
The following code compiles on Clang, MSVC, and ICC. But it fails on GCC.
https://godbolt.org/z/zHq0qi
#include
using
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: a-yee at u dot northwestern.edu
Target Milestone: ---
The following code leads to a strict-aliasing warning. But there is no aliasing
here.
https://godbolt.org/z/m2P_4-
Possibly
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: a-yee at u dot northwestern.edu
Target Milestone: ---
According to Intel's docs, all 4 of the AVX512 streaming instructions take void
pointers.
void _mm512_stream_ps (void* mem_addr, _
Assignee: unassigned at gcc dot gnu.org
Reporter: a-yee at u dot northwestern.edu
Target Milestone: ---
The following intrinsics are missing:
- _mm256_loadu2_m128()
- _mm256_storeu2_m128()
- _mm256_loadu2_m128d()
- _mm256_storeu2_m128d()
- _mm256_loadu2_m128i
: target
Assignee: unassigned at gcc dot gnu.org
Reporter: a-yee at u dot northwestern.edu
Target Milestone: ---
All the zero-extension intrinsics are missing: https://godbolt.org/z/JV8I51
#include
int main()
{
// 128 -> 256
_mm256_zextps128_ps256(_mm_setzero
