public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/riscv/heads/gcc-13-with-riscv-opts)] RISC-V: Reorder comment on SFB patterns Date: Wed, 22 Nov 2023 05:09:07 +0000 (GMT) [thread overview] Message-ID: <20231122050907.A90703858C53@sourceware.org> (raw) https://gcc.gnu.org/g:36abd417fb9b434a4b296e08d5cb0136f62286f4 commit 36abd417fb9b434a4b296e08d5cb0136f62286f4 Author: Maciej W. Rozycki <macro@embecosm.com> Date: Wed Nov 22 01:18:23 2023 +0000 RISC-V: Reorder comment on SFB patterns Our `mov<mode>cc' expander is no longer specific to short forward branch targets, so move its associated comment accordingly. gcc/ * config/riscv/riscv.md (mov<mode>cc): Move comment on SFB patterns over to... (*mov<GPR:mode><X:mode>cc): ... here. (cherry picked from commit 3bb4000c5f5f70cf5cb651314a939f1cbc65046d) Diff: --- gcc/config/riscv/riscv.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/config/riscv/riscv.md b/gcc/config/riscv/riscv.md index 1522b0b27cc..e6d90c2265f 100644 --- a/gcc/config/riscv/riscv.md +++ b/gcc/config/riscv/riscv.md @@ -2655,8 +2655,6 @@ [(set_attr "type" "branch") (set_attr "mode" "none")]) -;; Patterns for implementations that optimize short forward branches. - (define_expand "mov<mode>cc" [(set (match_operand:GPR 0 "register_operand") (if_then_else:GPR (match_operand 1 "comparison_operator") @@ -2671,6 +2669,8 @@ FAIL; }) +;; Patterns for implementations that optimize short forward branches. + (define_insn "*mov<GPR:mode><X:mode>cc" [(set (match_operand:GPR 0 "register_operand" "=r,r") (if_then_else:GPR
reply other threads:[~2023-11-22 5:09 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=20231122050907.A90703858C53@sourceware.org \ --to=law@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).