public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Wei Wu (吴伟)" <lazyparser@gmail.com>
To: gcc <gcc@gcc.gnu.org>,
	binutils@sourceware.org, gdb@sourceware.org,
	 libc-alpha@sourceware.org
Subject: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (Nov 18, 2021)
Date: Wed, 17 Nov 2021 21:51:36 +0800	[thread overview]
Message-ID: <CANkjrB5Z=X5BGJ0WSu_x1wA-zyHGb_yoq71abBqQ6M2+xncrQA@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:

- -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, Nov 18 2021
12:00a    Fri, Nov 19 2021

PST/PDT, Pacific Standard Time (US)
7:00a    Thu, Nov 18 2021
8:00a    Thu, Nov 18 2021

PHILADELPHIA, United States, Pennsylvania
10:00a    Thu, Nov 18 2021
11:00a    Thu, Nov 18 2021

-- 
Best wishes,
Wei Wu (吴伟)

                 reply	other threads:[~2021-11-17 13:52 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='CANkjrB5Z=X5BGJ0WSu_x1wA-zyHGb_yoq71abBqQ6M2+xncrQA@mail.gmail.com' \
    --to=lazyparser@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    /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).