From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) by sourceware.org (Postfix) with ESMTPS id 502A43857011; Wed, 10 Mar 2021 18:16:43 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 502A43857011 Received: by mail-oi1-x231.google.com with SMTP id w195so13489664oif.11; Wed, 10 Mar 2021 10:16:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=rLtdM7W+/XqR+4rxMDBGvIm6cYGafuRSmqhpctoGe5A=; b=aLfuEbaimfxPT2NFxuoqRS3jh36HcQq9L8x4/b1+EP+8hiZkCTisD+RHv0oau34cho zbIqvG9DjqwJucLxJUo+vZABn46ndzhjTTGt/0+mzTTdCBbjS8sl2Vc2QRXui+zlkk/V mkFbHSjtrow807omkSsBir8MVRIxVH6Zp/MKeUi5K4s2zBSQl7XCA3UnjO4c5EUYp++N 9NDWAuRtzgfBqCihuCnQmwFzWUuGqBl0bctCM/3LsBFBmnxD8F6vgWHFb0OQ7s5mt/ua R+Taem+qKnr5wicWETN1o+F/SIwawQWxcKRnMBjH8+zV8SHAQxS62ZbfW+zbIDq+/0E6 kV4Q== X-Gm-Message-State: AOAM531HAIY2YA+/aDPXOylu3l0TkeKsTstxlohcViT3Mx6NdWRMlFbQ eX31nGmHbhE3dIDpZ3FrP5GzhyNUO+BMnt+Fleo= X-Google-Smtp-Source: ABdhPJyVZO7GmVPcrvmX01DW4IVgZxbaeQFntW6K7PKt/6Y7r63cBAi5UvJEmc7H3Kw1EG8tf61wz2QIhDhpcsqRpWA= X-Received: by 2002:a54:480b:: with SMTP id j11mr3312219oij.116.1615400202796; Wed, 10 Mar 2021 10:16:42 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?V2VpIFd1ICjlkLTkvJ8p?= Date: Thu, 11 Mar 2021 02:16:03 +0800 Message-ID: Subject: Re: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up: Mar 11, 2021 To: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org, libc-alpha@sourceware.org, hellogcc@freelists.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=3.0 required=5.0 tests=BAYES_50, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TLD_CHINA, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2021 18:16:46 -0000 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 (=E5=90=B4=E4=BC=9F) wrote: > > Hi all, > > My name is Wei Wu. I am the project director of PLCT Lab, which is an eng= ineering team focusing on compilers, simulators, and virtual machines (runt= imes). The PLCT Lab is actively working on RISC-V toolchains, including GNU= Toolchain and Clang/LLVM. Recently, the PLCT Lab joined the RISC-V interna= tional as a group contributor[1]. We are working on implementing GCC/Binuti= ls for a few draft ISA extensions like Zfinx, Krypto Scalar, and P-extensio= n. > > I've noticed that there was no periodically sync-up meeting for RISC-V ba= ckend, and I think it might be good to have one[2][3]. I invite everyone wh= o is interested in RISC-V to join and have discussions, making the GNU Tool= chain 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=3DYm9mRHNkU2RDQ1VGOXVWMGJRR3Y3Zz09 > > Meeting ID: 829 0018 5885 > Passcode: 908375 > > All are welcome! > > [1] PLCT Lab is part of the Institute of Software, Chinese Academy of Sci= ences. So you may see that we are using the name CAS/PLCT in the RISC-V com= munity. > [2] Although the RISC-V community has its own task groups for ISA extensi= on, the discussion of the implementation details of specific compilers are = not encouraged. > [3] Thank Jeremy Bennett for this suggestion. -- Best wishes, Wei Wu (=E5=90=B4=E4=BC=9F)