public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	libc-alpha <libc-alpha@sourceware.org>,
	Siddhesh Poyarekar <siddhesh@redhat.com>
Subject: Re: glibc 2.34 - Hard ABI freeze effective immediately.
Date: Mon, 26 Jul 2021 09:00:31 -0400	[thread overview]
Message-ID: <8786a45d-c80d-0a28-1885-c2c7c28efa4a@redhat.com> (raw)
In-Reply-To: <4dc802d0-2660-d851-330d-6c8e56b08c88@linaro.org>

On 7/23/21 9:13 AM, Adhemerval Zanella wrote:
> 
> 
> On 23/07/2021 02:13, Carlos O'Donell wrote:
>> On 7/22/21 9:24 AM, Adhemerval Zanella wrote:
>>> Do we still have time for the posix_spawnattr_tcsetpgrp_np [1]? I think the
>>> code should be simple enough.
>>>
>>> [1] https://patchwork.sourceware.org/project/glibc/patch/20210617175751.1619846-2-adhemerval.zanella@linaro.org/
>> No, I do not think we have enough time, or to be more precise I want 
>> to review the use case, ask Godmar to verify that API does what is
>> required, and *then* include it in the release.
> 
> Fair enough.
> 
>>
>> I want to use the remaining 6 days to fix bugs without any further
>> ABI work.
>>
>> I would like to see:
>> - LD_AUDIT bugs fixed.
>> - pthread condvar bugs fixed.
>> - C.UTF-8 added as supported (resolved Florian's last comment about U+FFFD usage).
>>
> 
> I would like to add some extra time64 tests changes [1].  They do not touch
> the code, besides libsupport.
> 
> [1] https://patchwork.sourceware.org/project/glibc/list/?series=2510

Absolutely, we should review this and merge it.

I see the 32-bit builder failed this series:
NONE -> FAIL : socket/tst-socket-timestamp
NONE -> FAIL : socket/tst-socket-timestamp-time64


-- 
Cheers,
Carlos.


  reply	other threads:[~2021-07-26 13:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05  2:43 glibc 2.34 - Slushy " Carlos O'Donell
2021-07-19  2:15 ` glibc 2.34 - Hard ABI " Carlos O'Donell
2021-07-19 13:51   ` Florian Weimer
2021-07-19 14:13     ` Adhemerval Zanella
2021-07-19 14:30       ` Florian Weimer
2021-07-22 12:28         ` Carlos O'Donell
2021-07-22 13:02           ` Carlos O'Donell
2021-07-22 17:56             ` Florian Weimer
2021-07-22 12:31   ` Carlos O'Donell
2021-07-22 13:24     ` Adhemerval Zanella
2021-07-23  5:13       ` Carlos O'Donell
2021-07-23  5:53         ` Siddhesh Poyarekar
2021-07-26 14:22           ` Carlos O'Donell
2021-07-26 14:28             ` Samuel Thibault
2021-07-26 14:37               ` Siddhesh Poyarekar
2021-07-26 14:45                 ` Samuel Thibault
2021-07-23 13:13         ` Adhemerval Zanella
2021-07-26 13:00           ` Carlos O'Donell [this message]
2021-07-26 13:13             ` Adhemerval Zanella
2021-07-26 18:31             ` Adhemerval Zanella
2021-07-22 13:51     ` Siddhesh Poyarekar
2021-07-25 19:46   ` H.J. Lu
2021-07-25 21:54     ` Florian Weimer
2021-07-25 22:07       ` H.J. Lu
2021-07-25 22:14         ` Florian Weimer
2021-07-26  7:19         ` Andreas Schwab
2021-07-26 14:29     ` Carlos O'Donell
2021-07-26 14:32       ` H.J. Lu

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=8786a45d-c80d-0a28-1885-c2c7c28efa4a@redhat.com \
    --to=carlos@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@redhat.com \
    /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).