public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109807] [14 Regression] sse2-mmx-pmaddwd.c met ICE after commit r14-666-g608e7f3ab47 with march=cascadelake Date: Sun, 14 May 2023 19:59:17 +0000 [thread overview] Message-ID: <bug-109807-4-IVUd8iogRB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109807-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109807 Uroš Bizjak <ubizjak at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jamborm at gcc dot gnu.org --- Comment #15 from Uroš Bizjak <ubizjak at gmail dot com> --- *** Bug 109825 has been marked as a duplicate of this bug. ***
prev parent reply other threads:[~2023-05-14 19:59 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-11 6:25 [Bug target/109807] New: [14 Regression] sse2-mmx-pmaddwd.c met ICE after commit gcc-14-666-g608e7f3ab47 " haochen.jiang at intel dot com 2023-05-11 6:52 ` [Bug target/109807] [14 Regression] sse2-mmx-pmaddwd.c met ICE after commit r14-666-g608e7f3ab47 " haochen.jiang at intel dot com 2023-05-11 7:25 ` ubizjak at gmail dot com 2023-05-11 7:51 ` dcb314 at hotmail dot com 2023-05-11 7:53 ` haochen.jiang at intel dot com 2023-05-11 8:06 ` ubizjak at gmail dot com 2023-05-11 12:50 ` rguenth at gcc dot gnu.org 2023-05-11 15:42 ` ubizjak at gmail dot com 2023-05-11 18:55 ` cvs-commit at gcc dot gnu.org 2023-05-11 18:57 ` ubizjak at gmail dot com 2023-05-13 8:31 ` ubizjak at gmail dot com 2023-05-13 10:44 ` dcb314 at hotmail dot com 2023-05-13 10:50 ` ubizjak at gmail dot com 2023-05-14 19:53 ` cvs-commit at gcc dot gnu.org 2023-05-14 19:56 ` ubizjak at gmail dot com 2023-05-14 19:57 ` ubizjak at gmail dot com 2023-05-14 19:59 ` ubizjak at gmail dot com [this message]
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-109807-4-IVUd8iogRB@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).