From: jiawei@iscas.ac.cn
To: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org,
libc-alpha@sourceware.org
Cc: christoph.muellner@vrull.eu, 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, yulong@nj.iscas.ac.cn
Subject: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (June 30, 2022)
Date: Wed, 29 Jun 2022 22:53:50 +0800 (GMT+08:00) [thread overview]
Message-ID: <719a7d6c.35114.181aff446d2.Coremail.jiawei@iscas.ac.cn> (raw)
[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]
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:
- RVV supports status
RVV calling convention to aid lazy binding
https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/296
RVV register 'vxrm/vxsat' calling convention
https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/294
- RISC-V sub-extension supports status
Zawrs ISA extension patches
H-extension supported in binutils upstream
Patches for zfinx update
- Open topics
Wei Wu - PLCT Lab is inviting you to a scheduled Zoom meeting.
Topic: RISC-V GNU Toolchain Biweekly Sync-up
Time: June 30, 2022 11:00 PM Singapore
Please download and import the following iCalendar (.ics) files to your calendar system.
Weekly:
https://zoom.us/meeting/tZ0ufuqurjsjH9XTthkNg3MffX-QsRBuVBET/ics?icsToken=98tyKuGhrTIpHNSVuRyGRpx5A4r4b-7ziGJEgvplqAvtCA5UMS7wMNoPA6FNMs3m
Join Zoom Meeting
https://zoom.us/j/89393600951?pwd=ZFpWMkZ6Tm1TbUFXT1hZZjZZMHhRQT09
Meeting ID: 893 9360 0951
Passcode: 899662
BEIJING, China
11:00p Thu, June 30 2022
12:00a Fri, June 30 2022
PST/PDT, Pacific Standard Time (US)
8:00a Thu, June 30 2022
9:00a Thu, June 30 2022
PHILADELPHIA, United States, Pennsylvania
11:00a Thu, June 30 2022
12:00a Thu, June 30 2022
Paris, France
17:00p Thu, June 30 2022
18:00p Thu, June 30 2022
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: meeting-89393600951.ics --]
[-- Type: text/calendar; name=meeting-89393600951.ics, Size: 1690 bytes --]
BEGIN:VCALENDAR
PRODID:-//zoom.us//iCalendar Event//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
CLASS:PUBLIC
BEGIN:VTIMEZONE
TZID:Asia/Singapore
LAST-MODIFIED:20201011T015911Z
TZURL:http://tzurl.org/zoneinfo-outlook/Asia/Singapore
X-LIC-LOCATION:Asia/Singapore
BEGIN:STANDARD
TZNAME:+08
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
DTSTART:19700101T000000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20220309T112636Z
DTSTART;TZID=Asia/Singapore:20220310T230000
DTEND;TZID=Asia/Singapore:20220311T000000
SUMMARY:RISC-V GNU Toolchain Biweekly Sync-up
RRULE:FREQ=WEEKLY;WKST=SU;UNTIL=20220630T160000;INTERVAL=2;BYDAY=TH
UID:ZOOM89393600951
TZID:Asia/Singapore
DESCRIPTION:Wei Wu - PLCT Lab is inviting you to a scheduled Zoom meeting
.\n\nJoin Zoom Meeting\nhttps://us02web.zoom.us/j/89393600951?pwd=ZFpWMk
Z6Tm1TbUFXT1hZZjZZMHhRQT09\n\nMeeting ID: 893 9360 0951\nPasscode: 89966
2\nOne tap mobile\n+6531651065\,\,89393600951#\,\,\,\,*899662# Singapore
\n+6531587288\,\,89393600951#\,\,\,\,*899662# Singapore\n\nDial by your
location\n +65 3165 1065 Singapore\n +65 3158 7288 Singapo
re\n +1 669 900 9128 US (San Jose)\n +1 346 248 7799 US (H
ouston)\n +1 253 215 8782 US (Tacoma)\n +1 312 626 6799 US
(Chicago)\n +1 646 558 8656 US (New York)\n +1 301 715 85
92 US (Washington DC)\nMeeting ID: 893 9360 0951\nPasscode: 899662\nFind
your local number: https://us02web.zoom.us/u/kk9cyIPNJ\n\n
LOCATION:https://us02web.zoom.us/j/89393600951?pwd=ZFpWMkZ6Tm1TbUFXT1hZZj
ZZMHhRQT09
BEGIN:VALARM
TRIGGER:-PT10M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR
reply other threads:[~2022-06-29 14:53 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=719a7d6c.35114.181aff446d2.Coremail.jiawei@iscas.ac.cn \
--to=jiawei@iscas.ac.cn \
--cc=binutils@sourceware.org \
--cc=christoph.muellner@vrull.eu \
--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=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).