From: Noah Goldstein <goldstein.w.n@gmail.com>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>
Cc: libc-alpha@sourceware.org
Subject: Re: freeze for the upcoming glibc 2.38 release
Date: Thu, 13 Jul 2023 21:24:25 -0500 [thread overview]
Message-ID: <CAFUsyfLyrZ4HjhKg4-13kpHW_QbnoJmDjsf69PpcgQTpovOSWQ@mail.gmail.com> (raw)
In-Reply-To: <2308492.atdPhlSkOF@pinacolada>
On Thu, Jul 13, 2023 at 4:35 PM Andreas K. Huettel <dilfridge@gentoo.org> wrote:
>
> > > We still have two "desirables" on the wiki page,
> > > * "Add clone3 support for multiple architectures" - can we wrap this up
> > > safely next week?
> > > https://patchwork.sourceware.org/project/glibc/list/?series=16730
> > > * "Flip defaults for some security-relevant build configuration flags"
> > > https://patchwork.sourceware.org/project/glibc/list/?series=21908
> > > The series consists of 4 patches. 2 (stack-protector-strong), 3
> > > (bind-now) and 4 (disable-crypt) should be uncontroversial.
> > > ## The list thread on 1 (autoconf-2.71) ended without a clear
> > > conclusion. What's the status here? ##
> > >
> > > Anything else?
> >
> > I would like to make sure any necessary follow ups for tuning the
> > `non_temporal_threshold` on X86 machines gets into 2.38.
>
> Let's be careful and reluctant with pure performance tuning.
>
> Bug fixes are of course fine (and yes I know the boundary is somewhat
> ill-defined).
I think this one is more in the former category. At the very least want
to add a bound that ensure new number is never less than older value
(to avoid any blatant regressions). But hoping to hear from Sajan before
then to see if we can get a proper fix in.
>
> --
> Andreas K. Hüttel
> dilfridge@gentoo.org
> Gentoo Linux developer
> (council, toolchain, base-system, perl, libreoffice)
prev parent reply other threads:[~2023-07-14 2:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 18:28 Andreas K. Huettel
2023-07-06 18:43 ` Xi Ruoyao
2023-07-08 17:42 ` Andreas K. Huettel
2023-07-09 12:25 ` Xi Ruoyao
2023-07-07 7:29 ` Paul Zimmermann
2023-07-08 17:44 ` Andreas K. Huettel
2023-07-09 7:12 ` Paul Zimmermann
2023-07-07 10:18 ` Siddhesh Poyarekar
2023-07-08 17:46 ` Andreas K. Huettel
2023-07-07 12:12 ` Adhemerval Zanella Netto
2023-07-07 21:21 ` Andreas K. Huettel
2023-07-08 17:51 ` Andreas K. Huettel
2023-07-07 21:40 ` Andreas K. Huettel
2023-07-08 17:48 ` Andreas K. Huettel
2023-07-10 15:45 ` Adhemerval Zanella Netto
2023-07-10 16:06 ` Noah Goldstein
2023-07-13 21:35 ` Andreas K. Huettel
2023-07-14 2:24 ` Noah Goldstein [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=CAFUsyfLyrZ4HjhKg4-13kpHW_QbnoJmDjsf69PpcgQTpovOSWQ@mail.gmail.com \
--to=goldstein.w.n@gmail.com \
--cc=dilfridge@gentoo.org \
--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).