From: Eop Chen <eop.chen@sifive.com>
To: tech-rvv-intrinsics@lists.riscv.org
Cc: gcc@gcc.gnu.org, sig-toolchains@lists.riscv.org,
sig-hpc@lists.riscv.org, sig-graphics@lists.riscv.org,
tech-vector-ext@lists.riscv.org
Subject: RISC-V V C Intrinsic API v1.0 release meeting reminder (November 28th, 2022)
Date: Thu, 2 Feb 2023 22:22:27 +0800 [thread overview]
Message-ID: <CA4FE1B8-941E-444F-AAA8-1C5C8C9E8892@sifive.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
Hi all,
A reminder that the next open meeting to discuss on the RISC-V V C Intrinsic API v1.0 release is going to
be held later on 2022/02/02 6AM (GMT -7) / 11PM (GMT +8).
The agenda can be found in the second page of the meeting slides (link <https://docs.google.com/presentation/d/1q0fAg17gBH8_3VPiM6p9LW5q2PCsaXtqfwu1PtjfCZM/edit?usp=sharing>).
Please join the calendar to be constantly notified - Google calender link <https://calendar.google.com/calendar/embed?src=c_afjdibr5hpep8nosra3nnd7dgc%40group.calendar.google.com>, ICal <https://calendar.google.com/calendar/ical/c_afjdibr5hpep8nosra3nnd7dgc%40group.calendar.google.com/public/basic.ics>
We also have a mailing list now hosted by RISC-V International (link <https://lists.riscv.org/g/tech-rvv-intrinsics>).
Regards,
eop Chen
next reply other threads:[~2023-02-02 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 14:22 Eop Chen [this message]
2023-02-03 9:50 ` RISC-V V C Intrinsic API v1.0 release meeting reminder (February 2nd, 2022) Eop Chen
-- strict thread matches above, loose matches on Subject: below --
2022-11-27 17:04 RISC-V V C Intrinsic API v1.0 release meeting reminder (November 28th, 2022) eop Chen
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=CA4FE1B8-941E-444F-AAA8-1C5C8C9E8892@sifive.com \
--to=eop.chen@sifive.com \
--cc=gcc@gcc.gnu.org \
--cc=sig-graphics@lists.riscv.org \
--cc=sig-hpc@lists.riscv.org \
--cc=sig-toolchains@lists.riscv.org \
--cc=tech-rvv-intrinsics@lists.riscv.org \
--cc=tech-vector-ext@lists.riscv.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).