public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Maciej W. Rozycki <macro@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-1026] RISC-V: Use a tab rather than space with FSFLAGS Date: Thu, 9 Jun 2022 13:35:10 +0000 (GMT) [thread overview] Message-ID: <20220609133510.D68DC385277F@sourceware.org> (raw) https://gcc.gnu.org/g:702a11ade2e87515a7dda1d1c028217bfe28e609 commit r13-1026-g702a11ade2e87515a7dda1d1c028217bfe28e609 Author: Maciej W. Rozycki <macro@embecosm.com> Date: Thu Jun 9 14:34:34 2022 +0100 RISC-V: Use a tab rather than space with FSFLAGS Consistently use a tab rather than a space as the separator between the assembly instruction mnemonic and its operand with FSFLAGS instructions produced with the unordered FP comparison RTL insns. gcc/ * config/riscv/riscv.md (*f<quiet_pattern>_quiet<ANYF:mode><X:mode>4_default) (*f<quiet_pattern>_quiet<ANYF:mode><X:mode>4_snan): Emit a tab rather than space with FSFLAGS. 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 b8ab0cf169a..7745290383b 100644 --- a/gcc/config/riscv/riscv.md +++ b/gcc/config/riscv/riscv.md @@ -2344,7 +2344,7 @@ QUIET_COMPARISON)) (clobber (match_scratch:X 3 "=&r"))] "TARGET_HARD_FLOAT && ! HONOR_SNANS (<ANYF:MODE>mode)" - "frflags\t%3\n\tf<quiet_pattern>.<fmt>\t%0,%1,%2\n\tfsflags %3" + "frflags\t%3\n\tf<quiet_pattern>.<fmt>\t%0,%1,%2\n\tfsflags\t%3" [(set_attr "type" "fcmp") (set_attr "mode" "<UNITMODE>") (set (attr "length") (const_int 12))]) @@ -2357,7 +2357,7 @@ QUIET_COMPARISON)) (clobber (match_scratch:X 3 "=&r"))] "TARGET_HARD_FLOAT && HONOR_SNANS (<ANYF:MODE>mode)" - "frflags\t%3\n\tf<quiet_pattern>.<fmt>\t%0,%1,%2\n\tfsflags %3\n\tfeq.<fmt>\tzero,%1,%2" + "frflags\t%3\n\tf<quiet_pattern>.<fmt>\t%0,%1,%2\n\tfsflags\t%3\n\tfeq.<fmt>\tzero,%1,%2" [(set_attr "type" "fcmp") (set_attr "mode" "<UNITMODE>") (set (attr "length") (const_int 16))])
reply other threads:[~2022-06-09 13:35 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=20220609133510.D68DC385277F@sourceware.org \ --to=macro@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).