From: Philipp Tomsich <philipp.tomsich@vrull.eu>
To: Kito Cheng <kito.cheng@sifive.com>
Cc: Christoph Muellner <christoph.muellner@vrull.eu>,
gcc-patches@gcc.gnu.org, 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 Zawrs support
Date: Wed, 2 Nov 2022 19:58:41 +0100 [thread overview]
Message-ID: <CAAeLtUDM0_CW9v1uoyohiOYFGW3icz1W_VzU7TUGs1ZymxV76w@mail.gmail.com> (raw)
In-Reply-To: <CALLt3TjyhaK=snZ_SZ93Y7u8rTMWj7FW1oCg6KteV_58WfHuqQ@mail.gmail.com>
Applied to gcc-wwwdocs/master. Thanks!
Philipp.
On Wed, 2 Nov 2022 at 17:12, Kito Cheng <kito.cheng@sifive.com> wrote:
>
> LGTM, thanks!
>
> On Wed, Nov 2, 2022 at 7:59 AM Christoph Muellner
> <christoph.muellner@vrull.eu> wrote:
> >
> > From: Christoph Müllner <christoph.muellner@vrull.eu>
> >
> > This patch documents the new RISC-V Zawrs support.
> >
> > Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>
> > ---
> > htdocs/gcc-13/changes.html | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
> > index 7c6bfa6e..5e6e054b 100644
> > --- a/htdocs/gcc-13/changes.html
> > +++ b/htdocs/gcc-13/changes.html
> > @@ -261,7 +261,10 @@ a work-in-progress.</p>
> >
> > <!-- <h3 id="s390">S/390, System z, IBM z Systems</h3> -->
> >
> > -<!-- <h3 id="riscv">RISC-V</h3> -->
> > +<h3 id="riscv">RISC-V</h3>
> > +<ul>
> > + <li>New ISA extension support for zawrs.</li>
> > +</ul>
> >
> > <!-- <h3 id="rx">RX</h3> -->
> >
> > --
> > 2.38.1
> >
prev parent reply other threads:[~2022-11-02 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 14:59 Christoph Muellner
2022-11-02 16:11 ` Kito Cheng
2022-11-02 18:58 ` 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=CAAeLtUDM0_CW9v1uoyohiOYFGW3icz1W_VzU7TUGs1ZymxV76w@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@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).