From: Palmer Dabbelt <palmer@dabbelt.com>
To: Jeff Law <jlaw@ventanamicro.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
enh@google.com, dilfridge@gentoo.org, libc-alpha@sourceware.org
Subject: Re: Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release
Date: Wed, 10 Jan 2024 17:10:11 -0800 (PST) [thread overview]
Message-ID: <mhng-a3049b98-2431-4fb4-a4d8-bd05868be1dc@palmer-ri-x1c9> (raw)
In-Reply-To: <71096c2f-0974-4a4d-baa3-fcaa290440b5@ventanamicro.com>
On Wed, 10 Jan 2024 12:33:51 PST (-0800), Jeff Law wrote:
>
>
> On 1/10/24 11:38, Carlos O'Donell wrote:
>
>>>
>>> (speaking not as a glibc maintainer [or even user!], but as someone
>>> who aims for source compatibility where possible...) what's the status
>>> of the riscv64 ifunc stuff?
>>
>> Adding Palmer and Jeff to TO: to see if we have an answer for this.
> My recollection (from Cauldron) was that we were still waiting on a
> final approval for the first ifunc'd mem* routine as Florian had raised
> some correctness questions. The idea was once Florian's correctness
> questions were resolved we could use the knowledge to stamp out the
> other routines that have implementations, but needed the right ifunc glue.
>
> I haven't had the time to follow glibc at all the last few months. So
> if there's been movement I wouldn't be aware of it.
Evan has a patch set from this morning, I think it's ready to go. I'd
checked earlier this week too, but there were some comments.
So I think we can just commit it, it's been a pretty long tail of small
stuff.
>
>
> Jeff
next prev parent reply other threads:[~2024-01-11 1:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 13:18 Andreas K. Huettel
2024-01-02 9:14 ` Florian Weimer
2024-01-02 9:21 ` autoconf 2.72 ? (Re: Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release) Andreas K. Huettel
2024-01-02 10:27 ` Florian Weimer
2024-01-02 17:35 ` Paul Eggert
2024-01-02 19:17 ` [PATCH, test conversion, RFC] Convert to autoconf 2.72 (no patches) Andreas K. Hüttel
2024-01-02 21:30 ` Florian Weimer
2024-01-03 4:13 ` Paul Eggert
2024-01-10 18:37 ` Carlos O'Donell
2024-01-02 14:39 ` Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release Adhemerval Zanella Netto
2024-01-06 12:27 ` Andreas K. Huettel
2024-01-08 12:54 ` Adhemerval Zanella Netto
2024-01-02 15:22 ` H.J. Lu
2024-01-06 22:29 ` Andreas K. Huettel
2024-01-03 21:57 ` enh
2024-01-10 18:38 ` Carlos O'Donell
2024-01-10 20:33 ` Jeff Law
2024-01-11 1:10 ` Palmer Dabbelt [this message]
2024-01-12 6:13 ` Palmer Dabbelt
2024-01-11 22:24 ` Freeze for the upcoming glibc 2.39 release - status Andreas K. Huettel
2024-01-12 10:56 ` Adhemerval Zanella Netto
2024-01-12 13:14 ` Xi Ruoyao
2024-01-12 13:25 ` Andreas K. Huettel
2024-01-12 14:23 ` Andreas K. Huettel
2024-01-12 17:19 ` Carlos O'Donell
2024-01-12 17:34 ` Palmer Dabbelt
2024-01-12 18:10 ` Adhemerval Zanella Netto
2024-01-12 22:10 ` Palmer Dabbelt
2024-01-12 22:21 ` Freeze for the upcoming glibc 2.39 release - status (2) Andreas K. Huettel
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=mhng-a3049b98-2431-4fb4-a4d8-bd05868be1dc@palmer-ri-x1c9 \
--to=palmer@dabbelt.com \
--cc=carlos@redhat.com \
--cc=dilfridge@gentoo.org \
--cc=enh@google.com \
--cc=jlaw@ventanamicro.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).