From: eop Chen <eop.chen@sifive.com>
To: sig-toolchains@lists.riscv.org, sig-hpc@lists.riscv.org,
sig-graphics@lists.riscv.org, tech-vector-ext@lists.riscv.org,
gcc@gcc.gnu.org, tech-rvv-intrinsics@lists.riscv.org
Subject: Re: RISC-V V C Intrinsic API v1.0 release meeting reminder (October 31, 2022)
Date: Tue, 1 Nov 2022 00:59:16 +0800 [thread overview]
Message-ID: <03AD3892-5EFD-4758-A974-BC55FFCE4A6A@sifive.com> (raw)
In-Reply-To: <7A600713-D68B-4DEA-BB3A-43E1857FAB21@sifive.com>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
The meeting minutes in added in the note. <https://docs.google.com/document/d/19UucISxO9yuQcQ5S30g7wn2wV5D-1z0fA0GKNVOuktI/edit?usp=sharing>
You can also find it under riscv-admin/rvv-intrinsics. <https://github.com/riscv-admin/rvv-intrinsics/blob/main/meeting_minutes/2022_10_31.md>
> eop Chen <eop.chen@sifive.com> 於 2022年10月31日 上午12:57 寫道：
>
>
> 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 on 2022/10/31 7AM (GMT -7) / 10PM (GMT +8).
>
> The agenda can be found in the second page of the meeting slides (link <https://docs.google.com/presentation/d/1PjVehtwrT-WXfy0ZtFVvb3Yt45UOHLvjLW0CSNH7Bro/edit#slide=id.g15fdd3af7ec_2_242>).
> 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
>
prev parent reply other threads:[~2022-10-31 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 16:57 eop Chen
2022-10-31 14:02 ` eop Chen
2022-10-31 16:59 ` eop Chen [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=03AD3892-5EFD-4758-A974-BC55FFCE4A6A@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).