public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "evan@coeus-group.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99754] New: [sse2] new _mm_loadu_si16 and _mm_loadu_si32 implemented incorrectly Date: Wed, 24 Mar 2021 18:07:52 +0000 [thread overview] Message-ID: <bug-99754-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99754 Bug ID: 99754 Summary: [sse2] new _mm_loadu_si16 and _mm_loadu_si32 implemented incorrectly Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: evan@coeus-group.com Target Milestone: --- Created attachment 50470 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50470&action=edit Trivial patch _mm_loadu_si16 and _mm_loadu_si32 were implemented in GCC 11, but incorrectly. The value pointed to by the argument is supposed to go in the first element, but _mm_set_epi16 / _mm_set_epi32 reverse the argument order so in GCC they go in the *last* elemement. The most straightforward solution would be to change the _mm_set_* calls so the input is used for the last argument instead of the first (patch attached). FWIW, here is LLVM's implementation: <https://github.com/llvm/llvm-project/blob/a76d0207d5f94af698525d7dc1f0953ed35901a6/clang/lib/Headers/emmintrin.h#L1670-L1710>. I've verified that LLVM's implementation matches ICC's.
next reply other threads:[~2021-03-24 18:07 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-24 18:07 evan@coeus-group.com [this message] 2021-03-25 6:52 ` [Bug target/99754] " crazylht at gmail dot com 2022-03-11 15:15 ` peter at cordes dot ca 2022-03-11 15:21 ` peter at cordes dot ca 2022-03-11 15:53 ` jakub at gcc dot gnu.org 2022-03-14 9:45 ` cvs-commit at gcc dot gnu.org 2022-03-26 23:03 ` peter at cordes dot ca 2022-03-28 1:44 ` crazylht at gmail dot com 2022-03-28 2:33 ` cvs-commit at gcc dot gnu.org 2022-03-28 2:35 ` crazylht at gmail dot com 2022-05-07 7:26 ` 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-99754-4@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).