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/110227] [13/14 Regression] gcc generates invalid AVX-512 code Date: Tue, 13 Jun 2023 11:41:51 +0000 [thread overview] Message-ID: <bug-110227-4-R8W1njz6UQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110227-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110227 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Looking at that commit, it also introduced weird formatting: return "vpcmpeqd \t %t0, %t0, %t0"; and return "vpcmpeqd \t %x0, %x0, %x0"; and return "vpcmpeqd \t %x0, %x0, %x0"; definitely shouldn't have the spaces around \t on either side. But sure, agree the alternative with BH constraint on source should use x rather than v constraint on destination.
next prev parent reply other threads:[~2023-06-13 11:41 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-12 14:47 [Bug target/110227] New: " joseph.weening at gmail dot com 2023-06-12 14:51 ` [Bug target/110227] " joseph.weening at gmail dot com 2023-06-12 15:43 ` [Bug target/110227] [13/14 Regression] " pinskia at gcc dot gnu.org 2023-06-13 3:06 ` crazylht at gmail dot com 2023-06-13 11:41 ` jakub at gcc dot gnu.org [this message] 2023-06-13 13:55 ` rguenth at gcc dot gnu.org 2023-06-14 8:19 ` cvs-commit at gcc dot gnu.org 2023-06-14 8:20 ` cvs-commit at gcc dot gnu.org 2023-06-14 8:21 ` crazylht at gmail dot com 2023-07-27 9:26 ` rguenth at gcc dot gnu.org 2023-11-30 10:54 ` liuhongt 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-110227-4-R8W1njz6UQ@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).