public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99754] [sse2] new _mm_loadu_si16 and _mm_loadu_si32 implemented incorrectly Date: Fri, 11 Mar 2022 15:53:52 +0000 [thread overview] Message-ID: <bug-99754-4-zi76lEYkPl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99754-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99754 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-03-11 Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 52609 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52609&action=edit gcc12-pr99754.patch Full untested patch.
next prev parent reply other threads:[~2022-03-11 15:53 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-24 18:07 [Bug target/99754] New: " evan@coeus-group.com 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 [this message] 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-zi76lEYkPl@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).