public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Roger Sayle <sayle@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-1384] [Committed] Add constraints to new andn<dwi>_doubleword_bmi pattern in i386.md. Date: Fri, 1 Jul 2022 10:16:10 +0000 (GMT) [thread overview] Message-ID: <20220701101610.C8F3D3858D39@sourceware.org> (raw) https://gcc.gnu.org/g:e2d2a8ff4f0dd37336714a25623cc877cf5812b0 commit r13-1384-ge2d2a8ff4f0dd37336714a25623cc877cf5812b0 Author: Roger Sayle <roger@nextmovesoftware.com> Date: Fri Jul 1 11:14:12 2022 +0100 [Committed] Add constraints to new andn<dwi>_doubleword_bmi pattern in i386.md. Many thanks to Uros for spotting that I'd forgotten to add constraints to the new define_insn_and_split *andn<dwi>_doubleword_bmi when moving it from pre-reload to post-reload. I've pushed this obvious fix after a make bootstrap on x86_64-pc-linux-gnu. Sorry for the inconvenience to anyone building the tree with a non-default architecture that enables BMI. 2022-07-01 Roger Sayle <roger@nextmovesoftware.com> Uroš Bizjak <ubizjak@gmail.com> gcc/ChangeLog * config/i386/i386.md (*andn<mode>3_doubleword_bmi): Add constraints to post-reload define_insn_and_split. Diff: --- gcc/config/i386/i386.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md index 34018144e5f..352a21c585c 100644 --- a/gcc/config/i386/i386.md +++ b/gcc/config/i386/i386.md @@ -10405,10 +10405,10 @@ }) (define_insn_and_split "*andn<mode>3_doubleword_bmi" - [(set (match_operand:<DWI> 0 "register_operand") + [(set (match_operand:<DWI> 0 "register_operand" "=r") (and:<DWI> - (not:<DWI> (match_operand:<DWI> 1 "register_operand")) - (match_operand:<DWI> 2 "nonimmediate_operand"))) + (not:<DWI> (match_operand:<DWI> 1 "register_operand" "0")) + (match_operand:<DWI> 2 "nonimmediate_operand" "ro"))) (clobber (reg:CC FLAGS_REG))] "TARGET_BMI" "#"
reply other threads:[~2022-07-01 10:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220701101610.C8F3D3858D39@sourceware.org \ --to=sayle@gcc.gnu.org \ --cc=gcc-cvs@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).