public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Wei Wu (吴伟)" <lazyparser@gmail.com>
To: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org,
	 libc-alpha@sourceware.org, hellogcc@freelists.org
Subject: Re: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up: Mar 11, 2021
Date: Thu, 11 Mar 2021 02:16:03 +0800	[thread overview]
Message-ID: <CANkjrB75Wt30-4AqCnhg8Na=xL_2g-cXVabSw6K4Q7r6-n3_iA@mail.gmail.com> (raw)
In-Reply-To: <CANkjrB5dsubP_FFPYejBJPNDZDziLArjU_e1jGSXsDatHSwcVA@mail.gmail.com>

Hi all,

Topics to discuss on the first RISC-V GNU Toolchain sync-up meeting
include the following:
- Current status of the ISA extensions that PLCT Lab is working on.
- The idea and roadmap of all-in-one branches for developers.
- CI status and roadmap for riscv-gnu-toolchain and other GNU repos.
- Free discussion

On Thu, Feb 11, 2021 at 10:35 PM Wei Wu (吴伟) <lazyparser@gmail.com> wrote:
>
> Hi all,
>
> My name is Wei Wu. I am the project director of PLCT Lab, which is an engineering team focusing on compilers, simulators, and virtual machines (runtimes). The PLCT Lab is actively working on RISC-V toolchains, including GNU Toolchain and Clang/LLVM. Recently, the PLCT Lab joined the RISC-V international as a group contributor[1]. We are working on implementing GCC/Binutils for a few draft ISA extensions like Zfinx, Krypto Scalar, and P-extension.
>
> I've noticed that there was no periodically sync-up meeting for RISC-V backend, and I think it might be good to have one[2][3]. I invite everyone who is interested in RISC-V to join and have discussions, making the GNU Toolchain doing better on RISC-V.
>
> So the first sync-up meeting would happen on March 11, the agenda will be posted before the meeting:
>
> Topic: RISC-V GNU Toolchain Biweekly Sync-up
> Time: Mar 11, 2021 11:00 PM Beijing, Shanghai
>
> LOS ANGELES, United States, California
> 7:00a Thu, Mar 11 2021
> BEIJING, China
> 11:00p Thu, Mar 11 2021
> LONDON, United Kingdom, England
> 3:00p Thu, Mar 11 2021
> Join Zoom Meeting
> https://zoom.com.cn/j/82900185885?pwd=Ym9mRHNkU2RDQ1VGOXVWMGJRR3Y3Zz09
>
> Meeting ID: 829 0018 5885
> Passcode: 908375
>
> All are welcome!
>
> [1] PLCT Lab is part of the Institute of Software, Chinese Academy of Sciences. So you may see that we are using the name CAS/PLCT in the RISC-V community.
> [2] Although the RISC-V community has its own task groups for ISA extension, the discussion of the implementation details of specific compilers are not encouraged.
> [3] Thank Jeremy Bennett for this suggestion.



--
Best wishes,
Wei Wu (吴伟)

      reply	other threads:[~2021-03-10 18:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 14:35 Wei Wu (吴伟)
2021-03-10 18:16 ` Wei Wu (吴伟) [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='CANkjrB75Wt30-4AqCnhg8Na=xL_2g-cXVabSw6K4Q7r6-n3_iA@mail.gmail.com' \
    --to=lazyparser@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=hellogcc@freelists.org \
    --cc=libc-alpha@sourceware.org \
    /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).