From: jiawei@iscas.ac.cn
To: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org,
libc-alpha@sourceware.org
Cc: cmuellner@ventanamicro.com, jeremy.bennett@embecosm.com,
jim.wilson.gcc@gmail.com, kito.cheng@sifive.com,
nelson.chu@sifive.com, palmer@dabbelt.com,
philipp.tomsich@vrull.eu, wuwei2016@iscas.ac.cn,
shihua@iscas.ac.cn, sinan@isrc.iscas.ac.cn,
yulong@nj.iscas.ac.cn
Subject: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (Jan 27, 2022)
Date: Wed, 23 Feb 2022 21:01:41 +0800 (GMT+08:00) [thread overview]
Message-ID: <61dd2f2c.1fed6.17f26ac51d0.Coremail.jiawei@iscas.ac.cn> (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:
- Intrinsics common availability and naming rules discuss
- RISC-V subextension related implement progress
- Scalar Crypto extension supports status
- Zmmul extension supports status
- Zc*[1] extension supports status
- CMO extension supports on gcc part
- Open topics
Wei Wu - PLCT Lab is inviting you to a scheduled Zoom meeting.
Topic: RISC-V GNU Toolchain Biweekly Sync-up
Join Zoom Meeting
https://zoom.com.cn/j/89393600951?pwd=ZFpWMkZ6Tm1TbUFXT1hZZjZZMHhRQT09
Meeting ID: 893 9360 0951
Passcode: 899662
BEIJING, China
11:00p Thu, Feb 24 2022
12:00a Fri, Feb 24 2022
PST/PDT, Pacific Standard Time (US)
7:00a Thu, Feb 24 2022
8:00a Thu, Feb 24 2022
PHILADELPHIA, United States, Pennsylvania
10:00a Thu, Feb 24 2022
11:00a Thu, Feb 24 2022
next reply other threads:[~2022-02-23 13:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 13:01 jiawei [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-09 12:16 jiawei
2022-01-26 13:04 jiawei
2022-01-26 22:23 ` Philipp Tomsich
2022-01-27 16:18 ` Matthias Klose
2022-01-28 10:06 ` David Abdurachmanov
2022-01-28 12:29 ` Matthias Klose
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=61dd2f2c.1fed6.17f26ac51d0.Coremail.jiawei@iscas.ac.cn \
--to=jiawei@iscas.ac.cn \
--cc=binutils@sourceware.org \
--cc=cmuellner@ventanamicro.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jeremy.bennett@embecosm.com \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=libc-alpha@sourceware.org \
--cc=nelson.chu@sifive.com \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
--cc=shihua@iscas.ac.cn \
--cc=sinan@isrc.iscas.ac.cn \
--cc=wuwei2016@iscas.ac.cn \
--cc=yulong@nj.iscas.ac.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).