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 13, 2022)
Date: Wed, 12 Jan 2022 21:48:41 +0800 (GMT+08:00) [thread overview]
Message-ID: <4851e4f9.d59e.17e4e8c41a8.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:
- -misa-spec related issue:
- Bump default ISA spec to newer version, current default ISA spec
is 2.2, but it's already out-of-date for a long time
- The most impact is I ext. will bump to 2.1, which is
backward incompatible with 2.0, I 2.1 has split csr instruction to
zicsr ext. and ifence.i to zifencei ext., that might break some
existing build script.
- Discuss new scheme for -misa-spec or alternative scheme for
dealing with RISC-V profile
- Interaction between -march and RISC-V profile[1].
- Introduce -mprofile option: -mprofile=rvm20 + -march=rv32gc
- Or extend syntax of -march option like -march=rvm20+mafdc?
- RISC-V subextension related implement progress
[1] Note: What is RISC-V Profile: https://github.com/riscv/riscv-profiles/
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, Jan 13 2022
12:00a Fri, Jan 13 2022
PST/PDT, Pacific Standard Time (US)
7:00a Thu, Jan 13 2022
8:00a Thu, Jan 13 2022
PHILADELPHIA, United States, Pennsylvania
10:00a Thu, Jan 13 2022
11:00a Thu, Jan 13 2022
next reply other threads:[~2022-01-12 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 13:48 jiawei [this message]
2022-01-12 18:45 ` Palmer Dabbelt
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=4851e4f9.d59e.17e4e8c41a8.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).