public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/53192] Incorrect arguments to AVX2's gather intrinsics Date: Tue, 26 Mar 2024 23:00:50 +0000 [thread overview] Message-ID: <bug-53192-4-80p6ldFlyq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53192-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53192 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|wrong-code |diagnostic, rejects-valid Target|x86-64 |x86-64 (LP64) Status|WAITING |NEW --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. Here is a testcase which compiles just fine at -O0 but fails at -O1 and above: ``` #include <immintrin.h> __m128i f(long *base, __m128i vindx, int scale) { return _mm_i32gather_epi64 (base, vindx, 1); } __m128i g(long long *base, __m128i vindx, int scale) { return _mm_i32gather_epi64 (base, vindx, 1); } ``` Note clang's version is to always use a macro here. ICC directly defines these internally as real intrinsics and accepts the above without an error.
next prev parent reply other threads:[~2024-03-26 23:00 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-02 15:41 [Bug target/53192] New: " kirill.yukhin at intel dot com 2012-05-02 15:57 ` [Bug target/53192] " hjl.tools at gmail dot com 2012-05-22 9:57 ` kirill.yukhin at intel dot com 2012-05-22 10:13 ` kirill.yukhin at intel dot com 2012-05-22 12:33 ` jakub at gcc dot gnu.org 2012-05-22 12:38 ` jakub at gcc dot gnu.org 2024-03-26 23:00 ` pinskia at gcc dot gnu.org [this message] 2024-03-26 23:36 ` pinskia at gcc dot gnu.org 2024-03-27 13:38 ` jakub at gcc dot gnu.org 2024-03-27 13:40 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-53192-4-80p6ldFlyq@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).