From: Kito Cheng <kito.cheng@sifive.com>
To: Jeff Law <jlaw@ventanamicro.com>
Cc: Kito Cheng <kito.cheng@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
jeffreyalaw <jeffreyalaw@gmail.com>, palmer <palmer@dabbelt.com>,
vineetg <vineetg@rivosinc.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"Patrick O'Neill" <patrick@rivosinc.com>,
macro <macro@embecosm.com>, JojoR <rjiejie@linux.alibaba.com>
Subject: Re: RISC-V Bootstrap problems
Date: Thu, 25 May 2023 12:08:36 +0800 [thread overview]
Message-ID: <CALLt3TjQ5P45b5jptWvRcur4rYtbJfcX6fi-pCXNKjnx=0cRJA@mail.gmail.com> (raw)
In-Reply-To: <d669bf75-aa74-c9f7-1d2a-48b0c24a412f@ventanamicro.com>
Yeah, JoJo still working on toolchain stuff, but just not active on upstream GCC
cc. jojo
On Thu, May 25, 2023 at 12:06 PM Jeff Law <jlaw@ventanamicro.com> wrote:
>
>
>
> On 5/24/23 21:53, Kito Cheng wrote:
> > Jojo has a patch to try to split those things that should help this,
> > but seems not landed.
> >
> > https://patchwork.ozlabs.org/project/gcc/patch/20201104015315.81416-1-jiejie_rong@c-sky.com/
> Is JoJo still active? I haven't heard from JoJo in many months, perhaps
> as long as a year or two.
>
> Jeff
next prev parent reply other threads:[~2023-05-25 4:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 6:41 [PATCH] RISC-V: Add missing torture-init and torture-finish for rvv.exp Kito Cheng
2023-05-22 9:17 ` Kito Cheng
2023-05-23 3:52 ` Vineet Gupta
2023-05-24 18:18 ` Vineet Gupta
2023-05-24 20:34 ` Thomas Schwinge
2023-05-24 22:13 ` Vineet Gupta
2023-05-24 23:12 ` Vineet Gupta
2023-05-24 23:13 ` Palmer Dabbelt
2023-05-25 3:43 ` RISC-V Bootstrap problems Jeff Law
2023-05-25 3:46 ` juzhe.zhong
2023-05-25 3:53 ` Kito Cheng
2023-05-25 3:54 ` juzhe.zhong
2023-05-25 4:07 ` Jeff Law
2023-05-25 4:19 ` juzhe.zhong
2023-05-25 13:55 ` Jeff Law
2023-05-25 4:06 ` Jeff Law
2023-05-25 4:08 ` Kito Cheng [this message]
2023-05-25 3:51 ` juzhe.zhong
2023-05-24 23:15 ` [PATCH] RISC-V: Add missing torture-init and torture-finish for rvv.exp Jeff Law
2023-05-25 20:26 ` Thomas Schwinge
2023-05-26 23:38 ` Vineet Gupta
2023-05-30 18:43 ` Vineet Gupta
2023-05-31 16:28 ` Vineet Gupta
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='CALLt3TjQ5P45b5jptWvRcur4rYtbJfcX6fi-pCXNKjnx=0cRJA@mail.gmail.com' \
--to=kito.cheng@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=jlaw@ventanamicro.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=macro@embecosm.com \
--cc=palmer@dabbelt.com \
--cc=patrick@rivosinc.com \
--cc=rjiejie@linux.alibaba.com \
--cc=vineetg@rivosinc.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).