public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: glibc 2.35 - Status update: ABI freeze, and release blockers.
Date: Thu, 27 Jan 2022 10:53:07 +0100	[thread overview]
Message-ID: <87sft9pksc.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <3d98ce14-6c91-35c2-987b-73d0382ce39b@redhat.com> (Carlos O'Donell's message of "Thu, 27 Jan 2022 00:11:51 -0500")

* Carlos O'Donell:

> (a.2) glibc 2.34 ABI omission patch.
>
> Florian,
>
> What is the current status of the glibc 2.34 ABI omission patch?

I'm going to post a new version with or1k fixes (which have so far been
obscured by other build-many-glibcs.py failures).

> (b.1) Predictable ELF destructor ordering.
>
> Florian,
>
> We haven't had much time to review this, and I'd like to spend more
> time reviewing the changes and testing in Fedora. Would it be OK if
> we keep reviewing this and commit early in February? This would give
> us lots of time to include this in Fedora Rawhide and other rolling
> releases to look for issues.

That's okay.

We have two more issues that need investigation:

* The new terminal API for posix_spawn looks wrong to me (post
  forthcoming).

* The C.UTF-8 inconsistency reported by Michael Hudson-Doyle.

Thanks,
Florian


  reply	other threads:[~2022-01-27  9:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  5:11 Carlos O'Donell
2022-01-27  9:53 ` Florian Weimer [this message]
2022-01-27 16:15 ` Stefan Liebler

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=87sft9pksc.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=carlos@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).