From: Jeff Law <jeffreyalaw@gmail.com>
To: "Yixuan Chen" <oriachiuan@gmail.com>,
"Christoph Müllner" <christoph.muellner@vrull.eu>
Cc: Kito Cheng <kito.cheng@gmail.com>,
chenyixuan@iscas.ac.cn, gcc-patches@gcc.gnu.org,
shiyulong@iscas.ac.cn, shihua@iscas.ac.cn, jiawei@iscas.ac.cn,
Jojo R <rjiejie@linux.alibaba.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Cooper Qu <cooper.qu@linux.alibaba.com>
Subject: Re: [PATCH] minimal support for xtheadv
Date: Thu, 9 Nov 2023 09:04:05 -0700 [thread overview]
Message-ID: <ade60c32-fe0f-4b63-88a6-6150b9b6773f@gmail.com> (raw)
In-Reply-To: <CABLCG83g+th8yTxHzA-afDU5-BBu7WH2i9jusCtaq11C=3XUUQ@mail.gmail.com>
On 11/9/23 01:38, Yixuan Chen wrote:
> Hi Kito and Christoph,
>
> XYenChi (oriachiaun@gmail.com <mailto:oriachiaun@gmail.com>) is my
> e-mail address too. I didn't notice the git email config have changed,
> very sorry about that.
>
> We want to support other operate system project from our team, so port
> the XTheadV. If T-Head and VRULL have made great progress, it's pleasure
> to follow your work. By the way, I have sent the opcode patch to
> binutils, if you have any concern, please check the patch:
> https://sourceware.org/pipermail/binutils/2023-November/130431.html
> <https://sourceware.org/pipermail/binutils/2023-November/130431.html>
>
> If our team could provide any help, please let us know.
Given we see multiple organizations with an interest in this work, but
that the bulk of the work can't be integrated in the short term, y'all
might consider a shared development branch for coordination.
That gives the two organizations a place to coordinate their work while
things like the ISA spec and such get solidified. Presumably the goal
for the main body of work is not gcc-14, but gcc-15.
I don't want to dictate how coordination happens. Ultimately it's
something the relevant developers can decide.
jeff
next prev parent reply other threads:[~2023-11-09 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 13:12 chenyixuan
2023-11-09 7:39 ` Kito Cheng
2023-11-09 8:05 ` Christoph Müllner
2023-11-09 8:38 ` Yixuan Chen
2023-11-09 16:04 ` Jeff Law [this message]
2023-11-09 16:22 ` Kito Cheng
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=ade60c32-fe0f-4b63-88a6-6150b9b6773f@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=chenyixuan@iscas.ac.cn \
--cc=christoph.muellner@vrull.eu \
--cc=cooper.qu@linux.alibaba.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@gmail.com \
--cc=oriachiuan@gmail.com \
--cc=philipp.tomsich@vrull.eu \
--cc=rjiejie@linux.alibaba.com \
--cc=shihua@iscas.ac.cn \
--cc=shiyulong@iscas.ac.cn \
/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).