From: "Wei Wu (吴伟)" <lazyparser@gmail.com>
To: gcc <gcc@gcc.gnu.org>, binutils@sourceware.org, gdb@sourceware.org
Cc: "Kito Cheng" <kito.cheng@sifive.com>,
"Christoph Muellner" <cmuellner@ventanamicro.com>,
陈嘉炜 <jiawei@iscas.ac.cn>, "Nelson Chu" <nelson.chu@sifive.com>
Subject: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (June 3, 2021)
Date: Wed, 2 Jun 2021 20:36:23 +0800 [thread overview]
Message-ID: <CANkjrB4UjXc=XjGtQO1e91psnsSQPrGM7cLkwYgE0cu7wD4=aQ@mail.gmail.com> (raw)
Hi all,
There is an agenda for tomorrow's meeting. If you have topics to
discuss or share, please let me know and I can add them to the agenda.
## Agenda:
1 [RFC] Relax the canonical order checking of arch string for -march option
https://github.com/riscv/riscv-toolchain-conventions/issues/11
2 New vendor branch for RISC-V: integration and experimental branch
https://gcc.gnu.org/pipermail/gcc/2021-June/236229.html
3 The progress of Zce,Zfinx and B,P extentions in the toolchain part.
4 The progress of CI for GNU Toolchain
5 Free discussion
https://calendar.google.com/calendar/ical/lm5bddk2krcmtv5iputjgqvoio%40group.calendar.google.com/public/basic.ics
BEIJING, China
11:00p Thu, Jun 3 2021
12:00a Fri, Jun 4 2021
PDT/PST, Pacific Daylight Time (US)
8:00a Thu, Jun 3 2021
9:00a Thu, Jun 3 2021
LONDON, United Kingdom, England
4:00p Thu, Jun 3 2021
5:00p Thu, Jun 3 2021
Join Zoom Meeting
https://zoom.com.cn/j/89393600951?pwd=ZFpWMkZ6Tm1TbUFXT1hZZjZZMHhRQT09
Meeting ID: 893 9360 0951
Passcode: 899662
--
Best wishes,
Wei Wu (吴伟)
reply other threads:[~2021-06-02 12:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CANkjrB4UjXc=XjGtQO1e91psnsSQPrGM7cLkwYgE0cu7wD4=aQ@mail.gmail.com' \
--to=lazyparser@gmail.com \
--cc=binutils@sourceware.org \
--cc=cmuellner@ventanamicro.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@sifive.com \
--cc=nelson.chu@sifive.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).