From: jiawei@iscas.ac.cn
To: gcc <gcc@gcc.gnu.org>, binutils <binutils@sourceware.org>
Cc: "christoph.muellner" <christoph.muellner@vrull.eu>,
"jeremy.bennett" <jeremy.bennett@embecosm.com>,
"kito.cheng" <kito.cheng@sifive.com>,
palmer <palmer@dabbelt.com>,
nelson@rivosinc.com,
"philipp.tomsich" <philipp.tomsich@vrull.eu>,
wuwei2016 <wuwei2016@iscas.ac.cn>, shihua <shihua@iscas.ac.cn>,
shiyulong@iscas.ac.cn, chenyixuan@iscas.ac.cn
Subject: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (May 18, 2023)
Date: Wed, 17 May 2023 21:24:13 +0800 (GMT+08:00) [thread overview]
Message-ID: <31ae35e8.15b9.18829e1f36f.Coremail.jiawei@iscas.ac.cn> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1385 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 change the angenda/notes doc or let me know and I will update them, thanks.
https://docs.google.com/document/d/1JSs-BSlPJ3QYbAb-Add1TlbYx0nOT1ur3jcsITIJ01U/edit#
P.S. The meeting calendar .ics file has updated, please check and update it,thanks.
Agenda:
- New RISC-V ISA spec version
- RV64-ILP32 supports introduce
- Sub-extensions support status
- Open discuss
Wei Wu - PLCT Lab is inviting you to a scheduled Zoom meeting.
Topic: RISC-V GNU Toolchain Biweekly Sync-up
Time: May 18, 2023 UTC+0 15:00 / PST 07:00 / CST 23:00
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
23:00p Thu, May 18 2023
24:00a Fri, May 18 2023
PST/PDT, Pacific Standard Time (US)
8:00a Thu, May 18 2023
9:00a Thu, May 18 2023
PHILADELPHIA, United States, Pennsylvania
11:00a Thu, May 18 2023
12:00a Thu, May 18 2023
Paris, France
17:00p Thu, May 18 2023
18:00p Thu, May 18 2023
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: GNU-BIweekly-EN.ics --]
[-- Type: text/calendar; name=GNU-BIweekly-EN.ics, Size: 2087 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:20230104T023643Z
TZURL:https://www.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:20230215T105933Z
DTSTART;TZID=Asia/Singapore:20230223T230000
DTEND;TZID=Asia/Singapore:20230224T000000
SUMMARY:RISC-V GNU Toolchain Biweekly Sync-up
RRULE:FREQ=WEEKLY;WKST=SU;UNTIL=20231228T160000;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+6531294892\,\,89393600951#\,\,\,\,*899662# Singapore
\n+6531587288\,\,89393600951#\,\,\,\,*899662# Singapore\n\nDial by your
location\n +65 3129 4892 Singapore\n +65 3158 7288 Singapo
re\n +65 3165 1065 Singapore\n +65 3129 4891 Singapore\n
+1 669 900 9128 US (San Jose)\n +1 669 444 9171 US\n
+1 253 215 8782 US (Tacoma)\n +1 346 248 7799 US (Houston)\n
+1 719 359 4580 US\n +1 253 205 0468 US\n +1 386 347 5
053 US\n +1 507 473 4847 US\n +1 564 217 2000 US\n
+1 646 558 8656 US (New York)\n +1 646 931 3860 US\n +1 68
9 278 1000 US\n +1 301 715 8592 US (Washington DC)\n +1 30
5 224 1968 US\n +1 309 205 3325 US\n +1 312 626 6799 US (C
hicago)\n +1 360 209 5623 US\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:[~2023-05-17 13:24 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=31ae35e8.15b9.18829e1f36f.Coremail.jiawei@iscas.ac.cn \
--to=jiawei@iscas.ac.cn \
--cc=binutils@sourceware.org \
--cc=chenyixuan@iscas.ac.cn \
--cc=christoph.muellner@vrull.eu \
--cc=gcc@gcc.gnu.org \
--cc=jeremy.bennett@embecosm.com \
--cc=kito.cheng@sifive.com \
--cc=nelson@rivosinc.com \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
--cc=shihua@iscas.ac.cn \
--cc=shiyulong@iscas.ac.cn \
--cc=wuwei2016@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).