From: Kito Cheng <kito.cheng@gmail.com>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Andrew Waterman <andrew@sifive.com>
Subject: Re: [PING][PATCH] RISC-V: Standardize formatting of SFB ALU conditional move
Date: Thu, 18 Aug 2022 22:47:34 +0800 [thread overview]
Message-ID: <CA+yXCZDtjpaPH8yBdFmj9_g3rSOsy1DsWv8BP33qV19zJnqvNg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.2208181536280.19931@tpp.orcam.me.uk>
OK, thanks for tweaking this!
On Thu, Aug 18, 2022 at 10:40 PM Maciej W. Rozycki <macro@embecosm.com> wrote:
>
> On Tue, 26 Jul 2022, Maciej W. Rozycki wrote:
>
> > Standardize the formatting of SFB ALU conditional move operations from:
> >
> > beq a2,zero,1f; mv a0,zero; 1: # movcc
> >
> > to:
> >
> > beq a2,zero,1f # movcc
> > mv a0,zero
> > 1:
> >
> > for consistency with other assembly code produced. No functional change.
>
> Ping for:
> <https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598854.html>
>
> Maciej
next prev parent reply other threads:[~2022-08-18 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 18:38 [PATCH] " Maciej W. Rozycki
2022-08-18 14:40 ` [PING][PATCH] " Maciej W. Rozycki
2022-08-18 14:47 ` Kito Cheng [this message]
2022-08-18 15:54 ` Maciej W. Rozycki
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=CA+yXCZDtjpaPH8yBdFmj9_g3rSOsy1DsWv8BP33qV19zJnqvNg@mail.gmail.com \
--to=kito.cheng@gmail.com \
--cc=andrew@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=macro@embecosm.com \
/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: link
Be 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).