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-1858] RISC-V: Remove duplicate backslashes from `stack_protect_set_<mode>' Date: Wed, 27 Jul 2022 10:11:17 +0000 (GMT) [thread overview] Message-ID: <20220727101117.3F3B43857036@sourceware.org> (raw) https://gcc.gnu.org/g:3cf07cc5e51c833f39f5bad5ca6fbe23c853a214 commit r13-1858-g3cf07cc5e51c833f39f5bad5ca6fbe23c853a214 Author: Maciej W. Rozycki <macro@embecosm.com> Date: Wed Jul 27 11:09:43 2022 +0100 RISC-V: Remove duplicate backslashes from `stack_protect_set_<mode>' Remove redundant duplicate backslash characters from \t sequences in the output pattern of the `stack_protect_set_<mode>' RTL insn. gcc/ * config/riscv/riscv.md (stack_protect_set_<mode>): Remove duplicate backslashes. Diff: --- gcc/config/riscv/riscv.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/config/riscv/riscv.md b/gcc/config/riscv/riscv.md index 308b64dd30d..aa43d5f91a0 100644 --- a/gcc/config/riscv/riscv.md +++ b/gcc/config/riscv/riscv.md @@ -2848,7 +2848,7 @@ UNSPEC_SSP_SET)) (set (match_scratch:GPR 2 "=&r") (const_int 0))] "" - "<load>\\t%2, %1\;<store>\\t%2, %0\;li\t%2, 0" + "<load>\t%2, %1\;<store>\t%2, %0\;li\t%2, 0" [(set_attr "length" "12")]) (define_expand "stack_protect_test"
reply other threads:[~2022-07-27 10:11 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=20220727101117.3F3B43857036@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).