From: "Wei Wu (吴伟)" <lazyparser@gmail.com>
To: binutils@sourceware.org, gcc@gcc.gnu.org, gdb@sourceware.org
Cc: "Kito Cheng" <kito.cheng@sifive.com>, 陈嘉炜 <jiawei@iscas.ac.cn>,
"Christoph Muellner" <cmuellner@ventanamicro.com>,
"Jeremy Bennett" <jeremy.bennett@embecosm.com>,
wangtc@andestech.com, "Nelson Chu" <nelson.chu@sifive.com>
Subject: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (May 6, 2021)
Date: Wed, 5 May 2021 22:13:44 +0800 [thread overview]
Message-ID: <CANkjrB4m7fhTyEp6UoesOHybD3n1oBmv+XwsZgf0HVUFrvT0FQ@mail.gmail.com> (raw)
Hi all,
There is the 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. Status update for B, K, P, Zce, Zfinx extensions.
2. Zfinx ABI discussion
3. Revisit todo-list in the former code-speed-opt repos[1].
4. Discuss the status of CI Infrastructure for RISC-V backend and how
to improve/contribute.
5. AOB
[1] https://github.com/riscv/riscv-code-speed-optimization/blob/main/projects/gcc-optimizations.adoc
https://calendar.google.com/calendar/ical/lm5bddk2krcmtv5iputjgqvoio%40group.calendar.google.com/public/basic.ics
BEIJING, China
11:00p Thu, May 6 2021
12:00a Fri, May 7 2021
PDT/PST, Pacific Daylight Time (US)
8:00a Thu, May 6 2021
9:00a Thu, May 6 2021
LONDON, United Kingdom, England
4:00p Thu, May 6 2021
5:00p Thu, May 6 2021
Join Zoom Meeting
https://zoom.com.cn/j/89393600951?pwd=ZFpWMkZ6Tm1TbUFXT1hZZjZZMHhRQT09
Meeting ID: 893 9360 0951
Passcode: 899662
Find your local number: https://zoom.com.cn/u/kWo4yMmVQ
--
Best wishes,
Wei Wu (吴伟)
reply other threads:[~2021-05-05 14:14 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=CANkjrB4m7fhTyEp6UoesOHybD3n1oBmv+XwsZgf0HVUFrvT0FQ@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=jeremy.bennett@embecosm.com \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@sifive.com \
--cc=nelson.chu@sifive.com \
--cc=wangtc@andestech.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).