From: Jim Wilson <jimw@sifive.com>
To: PKU <yizhe@pku.edu.cn>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Having trouble getting my school to sign the copyright disclaimer
Date: Wed, 31 Mar 2021 10:22:03 -0700 [thread overview]
Message-ID: <CAFyWVab4G8g9c1aFEX4VTTGpGVFpCmTp01W-y7pmOs24n6yGEA@mail.gmail.com> (raw)
In-Reply-To: <784bc27b-d922-4c8f-bc2a-795361f79804@Spark>
On Wed, Mar 31, 2021 at 8:27 AM PKU via Gcc <gcc@gcc.gnu.org> wrote:
> I’m trying to get my school to sign the copyright disclaimer.
> Unfortunately the officials are reluctant to do that. Can anyone suggest
> what to do next?
>
Maybe the PLCT Lab at the Chinese Academy of Sciences can help. They are
doing GCC and LLVM work, and have GCC etc assignments. Even if they can't
help get an assignment for your current work, if you want to continue doing
GCC work, maybe your next patch can be written for them. They hold regular
meetings for people doing GCC/LLVM work in China to meet and discuss their
work. The PLCT work is primarily RISC-V focused though.
https://github.com/lazyparser/weloveinterns
https://github.com/lazyparser/weloveinterns/blob/master/open-internships.md#bj37-gccbinutilsglibclinker-%E5%BC%80%E5%8F%91%E5%AE%9E%E4%B9%A0%E7%94%9F-10%E5%90%8D
You might be able to find more appropriate links. I don't actually read
Mandarin. This is just a link I happen to know about which has good info
about the PLCT Lab.
Jim
prev parent reply other threads:[~2021-03-31 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <846257d9-b318-47dd-ad2f-08f1bd40b7a2@Spark>
2021-03-31 15:27 ` PKU
2021-03-31 15:32 ` David Edelsohn
2021-03-31 16:22 ` Richard Kenner
2021-03-31 17:22 ` Jim Wilson [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=CAFyWVab4G8g9c1aFEX4VTTGpGVFpCmTp01W-y7pmOs24n6yGEA@mail.gmail.com \
--to=jimw@sifive.com \
--cc=gcc@gcc.gnu.org \
--cc=yizhe@pku.edu.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).