From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: binutils@sourceware.org
Subject: Re: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (Oct 06, 2022)
Date: Thu, 6 Oct 2022 16:46:20 +0900 [thread overview]
Message-ID: <f3bdc19a-6b49-5de8-b485-a2cb9430c790@irq.a4lg.com> (raw)
In-Reply-To: <59c69b53.34374.183a8059817.Coremail.jiawei@iscas.ac.cn>
On 2022/10/05 21:01, 陈嘉炜 wrote:
> Hi all,
>
> Here is the agenda for tomorrow's RISC-V GNU toolchain meeting. If you have any topics want to
> discuss or share, please let me know and I will add them to the agenda, thanks.
>
>
>
> Agenda:
>
>
>
>
> - RISC-V in GNU Cauldron
>
>
>
>
> - Common framework for register pairs: Z[dq]inx and P-extension
My slides are available at:
https://docs.google.com/presentation/d/1TawtheXCS9RzIzGnKfl7T6q8P3LFsaj1S13lJVezco8/edit?usp=sharing
>
>
>
>
> - RISC-V sub-extension supports progress
>
>
>
>
> RVV gcc support progress
>
>
>
>
> Zmmul gcc support progress
>
>
>
>
> ZVFH extension support plan
>
>
>
>
> - Open discuss
>
>
> Wei Wu - PLCT Lab is inviting you to a scheduled Zoom meeting.
>
>
> Topic: RISC-V GNU Toolchain Biweekly Sync-up
> Time: Oct 06, 2022 11:00 PM Singapore
>
>
> Please download and import the following iCalendar (.ics) files to your calendar system.
>
>
> Weekly:
>
> https://calendar.google.com/calendar/ical/lm5bddk2krcmtv5iputjgqvoio%40group.calendar.google.com/public/basic.ics
>
>
>
> Join Zoom Meeting
> https://zoom.us/j/89393600951?pwd=ZFpWMkZ6Tm1TbUFXT1hZZjZZMHhRQT09
>
>
> Meeting ID: 893 9360 0951
> Passcode: 899662
>
>
> BEIJING, China
> 11:00p Thu, Oct 06 2022
>
>
> 12:00a Fri, Oct 06 2022
>
>
> PST/PDT, Pacific Standard Time (US)
> 8:00a Thu, Oct 06 2022
> 9:00a Thu, Oct 06 2022
>
> PHILADELPHIA, United States, Pennsylvania
> 11:00a Thu, Oct 06 2022
> 12:00a Thu, Oct 06 2022
>
> Paris, France
> 17:00p Thu, Oct 06 2022
> 18:00p Thu, Oct 06 2022
prev parent reply other threads:[~2022-10-06 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 12:01 陈嘉炜
2022-10-06 7:46 ` Tsukasa OI [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=f3bdc19a-6b49-5de8-b485-a2cb9430c790@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@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).