From: Philipp Tomsich <philipp.tomsich@vrull.eu>
To: Kito Cheng <kito.cheng@gmail.com>
Cc: Christoph Muellner <christoph.muellner@vrull.eu>,
gcc-patches@gcc.gnu.org, Kito Cheng <kito.cheng@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Waterman <andrew@sifive.com>
Subject: Re: [wwwdocs] gcc-13: riscv: Document the T-Head CPU support
Date: Wed, 15 Mar 2023 10:09:28 +0100 [thread overview]
Message-ID: <CAAeLtUC7zdu=E_2DdBF2e98Vk7vNPEnnHFJ2k5cB2H0qd6WGgg@mail.gmail.com> (raw)
In-Reply-To: <CA+yXCZD33qb5TXq-247RLoTrodLpQN_2_0Hi6av7AfvKRU3jhA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]
Applied to master, thanks!
Philipp.
On Sun, 5 Mar 2023 at 11:18, Kito Cheng <kito.cheng@gmail.com> wrote:
> LGTM :)
>
>
> On Fri, Feb 24, 2023 at 7:19 PM Christoph Muellner
> <christoph.muellner@vrull.eu> wrote:
> >
> > From: Christoph Müllner <christoph.muellner@vrull.eu>
> >
> > This patch documents the new T-Head CPU support for RISC-V.
> >
> > Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>
> > ---
> > htdocs/gcc-13/changes.html | 24 +++++++++++++++++++++++-
> > 1 file changed, 23 insertions(+), 1 deletion(-)
> >
> > diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
> > index a803f501..ce5ba35c 100644
> > --- a/htdocs/gcc-13/changes.html
> > +++ b/htdocs/gcc-13/changes.html
> > @@ -490,7 +490,29 @@ a work-in-progress.</p>
> >
> > <h3 id="riscv">RISC-V</h3>
> > <ul>
> > - <li>New ISA extension support for zawrs.</li>
> > + <li>New ISA extension support for Zawrs.</li>
> > + <li>Support for the following vendor extensions has been added:
> > + <ul>
> > + <li>XTheadBa</li>
> > + <li>XTheadBb</li>
> > + <li>XTheadBs</li>
> > + <li>XTheadCmo</li>
> > + <li>XTheadCondMov</li>
> > + <li>XTheadFMemIdx</li>
> > + <li>XTheadFmv</li>
> > + <li>XTheadInt</li>
> > + <li>XTheadMac</li>
> > + <li>XTheadMemIdx</li>
> > + <li>XTheadMemPair</li>
> > + <li>XTheadSync</li>
> > + </ul>
> > + </li>
> > + <li>The following new CPUs are supported through the
> <code>-mcpu</code>
> > + option (GCC identifiers in parentheses).
> > + <ul>
> > + <li>T-Head's XuanTie C906 (<code>thead-c906</code>).</li>
> > + </ul>
> > + </li>
> > </ul>
> >
> > <!-- <h3 id="rx">RX</h3> -->
> > --
> > 2.39.2
> >
>
prev parent reply other threads:[~2023-03-15 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 11:19 Christoph Muellner
2023-03-05 10:18 ` Kito Cheng
2023-03-15 9:09 ` Philipp Tomsich [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='CAAeLtUC7zdu=E_2DdBF2e98Vk7vNPEnnHFJ2k5cB2H0qd6WGgg@mail.gmail.com' \
--to=philipp.tomsich@vrull.eu \
--cc=andrew@sifive.com \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@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).