[Bug target/53192] Incorrect arguments to AVX2's gather intrinsics

2024-03-27 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53192 --- Comment #9 from Jakub Jelinek --- (In reply to Andrew Pinski from comment #7) > The other option is to change how intrinsics work on x86 and use resolve > overloads inside the backend like how aarch64, arm and rs6000 backends all > handle

[Bug target/53192] Incorrect arguments to AVX2's gather intrinsics

2024-03-27 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53192 --- Comment #8 from Jakub Jelinek --- Looking at other intrinsics with {,unsigned }__int64{, const} * arguments, I see void _mm_maskstore_epi64 (__int64* mem_addr, __m128i mask, __m128i a) void _mm256_maskstore_epi64 (__int64* mem_addr, __m256i

[Bug target/53192] Incorrect arguments to AVX2's gather intrinsics

2024-03-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53192 --- Comment #7 from Andrew Pinski --- (In reply to Jakub Jelinek from comment #5) > BTW, to avoid that warning, you could use in C: > extern __inline __m128i > __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) >

[Bug target/53192] Incorrect arguments to AVX2's gather intrinsics

2024-03-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53192 Andrew Pinski changed: What|Removed |Added Keywords|wrong-code |diagnostic, rejects-valid

[Bug target/53192] Incorrect arguments to AVX2's gather intrinsics

2012-05-22 Thread kirill.yukhin at intel dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53192 Yukhin Kirill kirill.yukhin at intel dot com changed: What|Removed |Added CC|

[Bug target/53192] Incorrect arguments to AVX2's gather intrinsics

2012-05-22 Thread kirill.yukhin at intel dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53192 --- Comment #2 from Yukhin Kirill kirill.yukhin at intel dot com 2012-05-22 08:22:12 UTC --- (In reply to comment #1) Please provide a testcase to show the problem. I have no idea, which kind of test it should be. These is just MS-ICC-GCC

[Bug target/53192] Incorrect arguments to AVX2's gather intrinsics

2012-05-22 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53192 Jakub Jelinek jakub at gcc dot gnu.org changed: What|Removed |Added CC||jakub at gcc dot

[Bug target/53192] Incorrect arguments to AVX2's gather intrinsics

2012-05-22 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53192 --- Comment #5 from Jakub Jelinek jakub at gcc dot gnu.org 2012-05-22 11:52:12 UTC --- BTW, to avoid that warning, you could use in C: extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_i32gather_epi64

[Bug target/53192] Incorrect arguments to AVX2's gather intrinsics

2012-05-02 Thread hjl.tools at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53192 H.J. Lu hjl.tools at gmail dot com changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last