From: Joseph Myers <josmyers@redhat.com>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>
Cc: Jakub Jelinek <jakub@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] v4: Use gcc __builtin_stdc_* builtins in stdbit.h if possible
Date: Wed, 31 Jan 2024 18:03:50 +0000 (UTC) [thread overview]
Message-ID: <e3e845a2-61d-b750-e381-010a2358443@redhat.com> (raw)
In-Reply-To: <2953861.VdNmn5OnKV@pinacolada>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
On Tue, 30 Jan 2024, Andreas K. Huettel wrote:
> > > Note that as we're currently in release freeze for glibc 2.39, a new
> > > feature change such as this should probably only go in before 2.39 is
> > > released with the approval of Andreas K. Hüttel as release manager (while
> > > if going in after 2.39 is released, the new feature of unsigned __int128 /
> > > unsigned _BitInt support should get a NEWS entry for 2.40).
> >
> > Andreas, your thoughts on whether this can be added to 2.39 or needs to wait
> > for 2.40? It is an extension to a new feature (stdbit.h has been added on
> > 3rd of January) and doesn't have ABI consequences.
>
> Hi Jakub, let's please do this after the release (i.e. for 2.40).
>
> I plan to branch tomorrow or wednesday, which means there is barely any time
> for wider testing anymore.
Now that 2.39 has branched, I think this can go in (with a NEWS entry
under "Major new features" for 2.40 to indicate it's a new user-visible
feature).
--
Joseph S. Myers
josmyers@redhat.com
next prev parent reply other threads:[~2024-01-31 18:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 18:04 [PATCH] " Jakub Jelinek
2024-01-20 23:27 ` Joseph Myers
2024-01-22 9:19 ` [PATCH] v2: " Jakub Jelinek
2024-01-22 17:58 ` Joseph Myers
2024-01-26 10:12 ` [PATCH] v3: " Jakub Jelinek
2024-01-29 21:07 ` Joseph Myers
2024-01-29 21:18 ` Jakub Jelinek
2024-01-29 21:30 ` Joseph Myers
2024-01-29 22:10 ` [PATCH] v4: " Jakub Jelinek
2024-01-30 0:28 ` Andreas K. Huettel
2024-01-31 18:03 ` Joseph Myers [this message]
2024-02-01 10:12 ` Mark Wielaard
2024-02-01 10:23 ` Mark Wielaard
2024-02-01 10:33 ` [PATCH] Fix up stdbit.texi Jakub Jelinek
2024-02-01 11:05 ` Mark Wielaard
2024-02-01 14:42 ` Carlos O'Donell
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=e3e845a2-61d-b750-e381-010a2358443@redhat.com \
--to=josmyers@redhat.com \
--cc=dilfridge@gentoo.org \
--cc=jakub@redhat.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).