From: "Wei Wu (吴伟)" <lazyparser@gmail.com>
To: gcc <gcc@gcc.gnu.org>, gdb@sourceware.org, libc-alpha@sourceware.org
Cc: "Kito Cheng" <kito.cheng@sifive.com>, 陈嘉炜 <jiawei@iscas.ac.cn>
Subject: Re: [RISCV] Call for topics: RISC-V GNU Toolchain Biweekly Sync-up call (July 1, 2021)
Date: Thu, 1 Jul 2021 09:40:22 +0800 [thread overview]
Message-ID: <CANkjrB6+r9-VnCX=ixHkVYpX791SdC6J8T_ckEFvLHQBU11hzg@mail.gmail.com> (raw)
In-Reply-To: <CANkjrB4yXW7Pfq4AqYX1zUX_kAa0WKQX=iUy6Z7yk+M0Z+z2sg@mail.gmail.com>
Hi all,
I've just noticed that the meeting time conflicted with the monthly
meeting of the software standing committee of RISC-V International.
So I'd like to skip today's meeting. The next meeting time is July 15.
Sorry for the inconvenience.
On Wed, Jun 30, 2021 at 10:52 PM Wei Wu (吴伟) <lazyparser@gmail.com> wrote:
>
> Hi all,
>
> Agenda:
> 1. Relax the ISA string order checking for -march
> - https://github.com/riscv/riscv-toolchain-conventions/pull/14Zfinx ABI
> - https://github.com/riscv/riscv-elf-psabi-doc/pull/189Mapping symbol
> - https://sourceware.org/pipermail/binutils/2021-May/116803.htmlRFC:
> New attribute for reserved register
> - Initial demand comes from overlay ABI, but it seems could be
> generalized for more general purpose.
> 2. Status update for Unratified Specs
> 3. Free Discussion.
>
> Wei Wu - PLCT Lab is inviting you to a scheduled Zoom meeting.
>
> Topic: RISC-V GNU Toolchian Biweekly Sync-up
> Time: Jul 1, 2021 11:00 PM Singapore
>
> Please download and import the following iCalendar (.ics) files to
> your calendar system.
> Weekly: https://zoom.com.cn/meeting/tZ0ufuqurjsjH9XTthkNg3MffX-QsRBuVBET/ics?icsToken=98tyKuGhrTIpHNSVuRyGRpx5A4r4b-7ziGJEgvplqAvtCA5UMS7wMNoPA6FNMs3m
>
> Join Zoom Meeting
> https://zoom.com.cn/j/89393600951?pwd=ZFpWMkZ6Tm1TbUFXT1hZZjZZMHhRQT09
>
> Meeting ID: 893 9360 0951
> Passcode: 899662
>
>
> On Wed, Jun 30, 2021 at 8:48 PM Wei Wu (吴伟) <lazyparser@gmail.com> wrote:
> >
> > Hi all,
> >
> > We may skip tomorrow's RISC-V GNU Biweekly meeting, for not so many
> > topics were collected. Please reply this email if you have several
> > topics to discuss, otherwise I'd like to skip tomorrow's meeting.
> >
> > --
> > Best wishes,
> > Wei Wu (吴伟)
>
>
>
> --
> Best wishes,
> Wei Wu (吴伟)
--
Best wishes,
Wei Wu (吴伟)
prev parent reply other threads:[~2021-07-01 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 12:48 Wei Wu (吴伟)
2021-06-30 14:52 ` Wei Wu (吴伟)
2021-07-01 1:40 ` Wei Wu (吴伟) [this message]
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='CANkjrB6+r9-VnCX=ixHkVYpX791SdC6J8T_ckEFvLHQBU11hzg@mail.gmail.com' \
--to=lazyparser@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@sifive.com \
--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).