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
Subject: Re: RISC-V V C Intrinsic API v1.0 release meeting reminder (Sep 05, 2022)
Date: Tue, 6 Sep 2022 01:08:40 +0800 [thread overview]
Message-ID: <3D299183-4D19-41B0-9A29-DC3229C3CCB3@sifive.com> (raw)
In-Reply-To: <DC1E7E9A-52C4-4AB8-8021-2B7D774C23D4@sifive.com>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
The meeting minute is updated in the document of the Google calendar link. <https://docs.google.com/document/d/19UucISxO9yuQcQ5S30g7wn2wV5D-1z0fA0GKNVOuktI/edit?usp=sharing>
Regards,
eop Chen
> eop Chen <eop.chen@sifive.com> 於 2022年9月1日 下午1:15 寫道：
>
>
> Hi all,
>
> A reminder that an open meeting to draft the RISC-V V C Intrinsic API v1.0 release is going to
> be held on next Monday 2022/09/05 7AM (GMT -7) / 10PM (GMT +8). The planned agenda will
> be to have a roundtable of introductions for participants and briefly go over milestones for
> v1.0 release so we can extend the discussions offline in the issue threads.
>
> 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>
>
> Regards,
>
> eop Chen
prev parent reply other threads:[~2022-09-05 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 5:15 eop Chen
2022-09-01 5:15 ` eop Chen
2022-09-05 17:08 ` 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=3D299183-4D19-41B0-9A29-DC3229C3CCB3@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-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).