From: Jeff Law <jeffreyalaw@gmail.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH -next v18 00/20] riscv: Add vector ISA support
Date: Sun, 30 Apr 2023 15:23:31 -0600 [thread overview]
Message-ID: <061c5d19-1746-3faa-f672-a9bb83815186@gmail.com> (raw)
In-Reply-To: <mhng-47aa965a-2b25-4ac0-984a-c2e6f3a051ee@palmer-ri-x1c9>
On 4/26/23 08:27, Palmer Dabbelt wrote:
>
> A few of us were talking in the patchwork meeting. It's kind of a grey
> area here, but we're just going to play it safe and wait for the prctl
> and sys interfaces to show up before merging this.
>
> I know it's a pain to have to wait another release, but there's still no
> publicly availiable V hardware yet so waiting isn't concretely impacting
> users right now. If we flip on V now we probably won't get a ton of
> testing, so we risk the ABI break sticking around for a few release
> which would be a huge headache.
>
> Andy said he'd be able to do the prtcl and sys interfaces pretty
> quickly, so hopfully everything's lined up for the next release.
From a scheduling standpoint, it would be best if we could have the
glibc side wrapped up over the next 2-3 months. That way the bits make
the August glibc release. Obviously we need to have a suitable fallback
path when running with old kernels.
Jeff
prev parent reply other threads:[~2023-04-30 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230414155843.12963-1-andy.chiu@sifive.com>
2023-04-19 7:43 ` Björn Töpel
2023-04-19 14:54 ` Björn Töpel
2023-04-19 15:18 ` Palmer Dabbelt
2023-04-20 16:36 ` Andy Chiu
2023-04-26 14:27 ` Palmer Dabbelt
2023-04-30 21:23 ` Jeff Law [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=061c5d19-1746-3faa-f672-a9bb83815186@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=libc-alpha@sourceware.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).