public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Kito Cheng <kito.cheng@sifive.com>,
	gcc-patches@gcc.gnu.org, palmer@dabbelt.com
Subject: Re: [PATCH] doc: Add doc for RISC-V Operand Modifiers
Date: Mon, 10 Jul 2023 22:51:08 +0800	[thread overview]
Message-ID: <CA+yXCZBmxem-AxhfTn6-exbWA7KFCavUaeNii_agyZvYQGOo7Q@mail.gmail.com> (raw)
In-Reply-To: <3684e257-a776-3971-0417-2a8c553e299d@gmail.com>

thanks, pushed to trunk :)

On Mon, Jul 10, 2023 at 10:33 PM Jeff Law via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
>
>
> On 7/10/23 08:19, Kito Cheng wrote:
> > Document `z` and `i` operand modifiers, we have much more modifiers
> > other than those two, but they are the only two implement on both
> > GCC and LLVM, consider the compatibility I would like to document those
> > two first, and then review other modifiers later to see if any other should
> > expose and implement on RISC-V LLVM too.
> >
> > gcc/ChangeLog:
> >
> >       * doc/extend.texi (RISC-V Operand Modifiers): New.
> OK
> jeff

      reply	other threads:[~2023-07-10 14:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 14:19 Kito Cheng
2023-07-10 14:32 ` Jeff Law
2023-07-10 14:51   ` Kito Cheng [this message]

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+yXCZBmxem-AxhfTn6-exbWA7KFCavUaeNii_agyZvYQGOo7Q@mail.gmail.com \
    --to=kito.cheng@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=palmer@dabbelt.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).