public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jojo R <rjiejie@linux.alibaba.com>
To: Palmer Dabbelt <palmer@dabbelt.com>, Jim Wilson <jimw@sifive.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/2] RISC-V: Add arch flags for T-HEAD.
Date: Thu, 22 Jul 2021 10:16:33 +0800	[thread overview]
Message-ID: <38d64b8a-b0d0-4866-8534-7e14db936466@Spark> (raw)
In-Reply-To: <CAFyWVaYnj+U6umtZBw7Hep2S9SjfTt3eDvEm4CgsbHv7j55Kmw@mail.gmail.com>


— Jojo
在 2021年7月22日 +0800 AM4:53,Jim Wilson <jimw@sifive.com>,写道:
> On Tue, Jul 13, 2021 at 11:06 AM Palmer Dabbelt <palmer@dabbelt.com> wrote:
> > Is there are documentation as to what this "theadc" extension is?
>
> The best doc I know of is    https://github.com/isrc-cas/c910-llvmThe README is in Chinese, but google translate does a decent job on it.  If you want more details, you have to read the llvm sources to see exactly what each instruction does.  They have mentioned that they are working on English language docs, but I don't know when they will be available.
> There are quite a few T-Head specific instructions here.  This patch is only adding support for a few of them, probably as a trial to see how it goes before they try to add the rest.
Hi,

	Please let me feed more details for this patch,

	There are about ~100+ instructions in our ISA spec,
	and we put the RFC[1] to ask guide how to commit vendor extension ISAs,
	we want to commit one type instruction every time, it’s helpful for reviewing.

	Some Chinese T-HEAD ISA Specs have been on the our web page [2] already,
	and we are converting these docs to english version to help your reading :)
	it will be out in the next week, including binutils.

	Thanks for your suggestion of the patch

[1] https://github.com/riscv/riscv-gcc/issues/278
[2] https://www.t-head.cn/technology
> Jim
>

  reply	other threads:[~2021-07-22  2:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29  8:11 [PATCH 0/2] RISC-V: Add ldr/str instruction " Jojo R
2021-06-29  8:11 ` [PATCH 1/2] RISC-V: Add arch flags " Jojo R
2021-07-13 18:06   ` Palmer Dabbelt
2021-07-21 20:53     ` Jim Wilson
2021-07-22  2:16       ` Jojo R [this message]
2021-08-27  3:22         ` Jojo R
2021-06-29  8:11 ` [PATCH 2/2] RISC-V: Add ldr/str instruction " Jojo R
2021-07-13 18:06   ` Palmer Dabbelt
2021-07-09  1:30 ` [PATCH 0/2] " ALO
2021-07-11  2:31   ` ALO
2021-07-13 18:06     ` Palmer Dabbelt

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=38d64b8a-b0d0-4866-8534-7e14db936466@Spark \
    --to=rjiejie@linux.alibaba.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jimw@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).