public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: dilfridge@gentoo.org, libc-alpha@sourceware.org,
	adhemerval.zanella@linaro.org, fweimer@redhat.com,
	Jeff Law <jlaw@ventanamicro.com>, H.J. Lu <hjl.tools@gmail.com>
Subject: Re: Freeze for the upcoming glibc 2.39 release - status
Date: Fri, 12 Jan 2024 09:34:12 -0800 (PST)	[thread overview]
Message-ID: <mhng-367b3703-6779-4798-b5f7-eb08e054343f@palmer-ri-x1c9> (raw)
In-Reply-To: <1be54729-05ea-0b4f-3f2c-093df775cf6a@redhat.com>

On Fri, 12 Jan 2024 09:19:14 PST (-0800), Carlos O'Donell wrote:
> On 1/11/24 17:24, Andreas K. Huettel wrote:
>> [PATCH v2] stdlib: Reinstate stable mergesort implementation on qsort
>> https://patchwork.sourceware.org/project/glibc/list/?series=29039
>> delegated, Florian is looking at this
>> release blocker
>
> Agreed. Florian is reviewing this.
>
>> [PATCH v2] linux: Fix fstat64 on alpha and sparc64
>> https://patchwork.sourceware.org/project/glibc/list/?series=29040
>> needs review
>> release blocker
>
> I have just reviewed this.
>
> Adhemerval, Please commit.
>
>> [PATCH v2] Make __getrandom_nocancel set errno and add a _nostatus version
>> https://patchwork.sourceware.org/project/glibc/list/?series=29130
>> R-B Adhemerval
>> bug fix - should go in now?
>
> Agreed.
>
>> [PATCH] debug/getwd_chk.c: warning should be emitted for the __getwd_chk symbol
>> https://patchwork.sourceware.org/project/glibc/list/?series=27941
>> R-B Adhemerval
>> bug fix - should go in now
>>
>
> Agreed.
>
>> [PATCH v3] RISC-V: Enable static-pie
>> https://patchwork.sourceware.org/project/glibc/list/?series=29034
>> R-B Adhemerval
>> feature - could be in already - now or after release?
>
> Agreed. It should go in ASAP.
>
> Adhemerval, Will you commit this?
>
>
>> [PATCH] math: remove exp10 wrappers
>> https://patchwork.sourceware.org/project/glibc/list/?series=29463
>> R-B Adhemerval
>> feature - could go in now, last minute for it
>
> Agreed. This should go in ASAP.
>
>> [PATCH v11 0/7] RISC-V: ifunced memcpy using new kernel hwprobe interface
>> https://patchwork.sourceware.org/project/glibc/list/?series=29471
>> needs another review?
>> lots of code, but already many iterations - soon or after release
>
> My feeling is that this should go in as soon as 2.40 opens.
>
> It introduces too many generic changes to make me comfortable for 2.39 right now.

OK, good timing -- my i686-gnu build just passed, so I was rebasing to 
commit stuff.  I'm not super opposed to holding off, it's pretty late in 
the cycle, but we'll probably end up with a bit of user headaches as 
folks will likely just call the syscall directly.

I'll hold off on commiting it unless folks feel like we should pick it 
up, just let me know...

>
>> [PATCH] x86-64: Check if mprotect works before rewriting PLT
>> https://patchwork.sourceware.org/project/glibc/list/?series=29560
>> needs review / discussion?
>
> Reviewed and needs a v2.
>
> HJ, Please review my comments.
>
>> [PATCH v3] rtld: Add glibc.rtld.enable_secure tunable
>> https://patchwork.sourceware.org/project/glibc/list/?series=29055
>> needs review, test failure
>> feature - after release
>
> Agreed. This is glibc 2.40 material at this point.

  reply	other threads:[~2024-01-12 17:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-01 13:18 Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release 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
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 [this message]
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-367b3703-6779-4798-b5f7-eb08e054343f@palmer-ri-x1c9 \
    --to=palmer@dabbelt.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=dilfridge@gentoo.org \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.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).