From: eop Chen <eop.chen@sifive.com>
To: 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, sig-vector@lists.riscv.org
Subject: Re: RISC-V V C Intrinsic API v1.0 release meeting reminder (Oct 03, 2022)
Date: Tue, 4 Oct 2022 03:09:26 +0800 [thread overview]
Message-ID: <7AF62F8A-0E84-43C7-9C0F-B9FDCB7A12EB@sifive.com> (raw)
In-Reply-To: <DE5C3148-6FA5-4A60-A968-3F942D473E90@sifive.com>
[-- Attachment #1: Type: text/plain, Size: 996 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>
> eop Chen <eop.chen@sifive.com> 於 2022年10月3日 下午8:57 寫道：
>
> 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 later on 2022/10/03 7AM (GMT -7) / 10PM (GMT +8).
>
> Slide has been posted and agenda is in the second page [0].
>
> Please join the calendar to be constantly notified - Google calender link <https://calendar.google.com/calendar/embed?src=c_afjdibr5hpep8nosra3nnd7dgc@group.calendar.google.com> , ICal <https://calendar.google.com/calendar/ical/c_afjdibr5hpep8nosra3nnd7dgc@group.calendar.google.com/public/basic.ics>.
>
> [0] Link to meeting notes and slides <https://docs.google.com/document/d/19UucISxO9yuQcQ5S30g7wn2wV5D-1z0fA0GKNVOuktI/edit?usp=sharing>
>
> Regards,
>
> eop Chen
>
>
>
prev parent reply other threads:[~2022-10-03 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 12:57 eop Chen
2022-10-03 13:29 ` [RISC-V] [sig-toolchains] " Mark Himelstein
2022-10-03 19:09 ` 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=7AF62F8A-0E84-43C7-9C0F-B9FDCB7A12EB@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=sig-vector@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).