This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.30 - 6 days until ABI freeze.
- From: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
- To: Mike Crowe <mac at mcrowe dot com>
- Cc: Carlos O'Donell <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, Alistair Francis <alistair dot francis at wdc dot com>, Carlos O'Donell <carlos at redhat dot com>, Florian Weimer <fweimer at redhat dot com>
- Date: Thu, 4 Jul 2019 11:39:34 -0300
- Subject: Re: glibc 2.30 - 6 days until ABI freeze.
- References: <c844bfaf-e459-1b6c-3bf2-81adb1ea3a0b@redhat.com> <20190628112223.t72h4yvkyqfgnccc@mcrowe.com> <c8d030aa-3567-adbc-164a-ffd696644abd@redhat.com> <20190628121052.doay6vsfc56xi24v@mcrowe.com> <82eba936-25ad-4ad3-15c2-842313113b10@redhat.com> <43d08e80-bcaa-8426-c0a1-283da9a0eaf2@linaro.org> <20190704143033.vuvsmmlvke7bsiug@mcrowe.com>
On 04/07/2019 11:30, Mike Crowe wrote:
> On Thursday 04 July 2019 at 10:39:05 -0300, Adhemerval Zanella wrote:
>>
>>
>> On 28/06/2019 09:55, Carlos O'Donell wrote:
>>> On 6/28/19 8:10 AM, Mike Crowe wrote:
>>>> On Friday 28 June 2019 at 07:58:21 -0400, Carlos O'Donell wrote:
>>>>> On 6/28/19 7:22 AM, Mike Crowe wrote:
>>>>>> On Monday 24 June 2019 at 21:45:48 -0400, Carlos O'Donell wrote:
>>>>>>> We have 6 days until the ABI freeze for glibc 2.30.
>>>>>>
>>>>>> Adhemerval Zanella and I would quite like to get the new pthread _clock
>>>>>> versions of existing _timed functions in. The changes are currently sat on
>>>>>> the azanella/master-posix_clock branch.
>>>>>
>>>>> How close are we to done that review?
>>>>
>>>> I think that the patches themselves are in very good shape (thanks to
>>>> Adhemerval fixing up all my bad formatting.)
>>>>
>>>> The delay is due to some last-minute worries[1] that the functions might
>>>> need to have _np suffixes on them until they're actually formally part of
>>>> POSIX. I think that the chance of the function names or parameters changing
>>>> at this stage is low, but I'm not an expert in the standardisation process.
>>>
>>> If you use _np suffixes you won't have to worry about this at all, and then
>>> we can alias the the new functions when updated.
>>>
>>>> Thanks.
>>>>
>>>> Mike.
>>>>
>>>> [1] https://sourceware.org/ml/libc-alpha/2019-06/msg00765.html
>>
>> Hi Carlos, should I assume your take on this is for 2.30 we add the _np suffixes?
>>
>> Mike, if this were the case, could you change the names based on my personal
>> branch?
>
> I can do that, but given the previous support for the unadorned names I was
> hoping for more responses from others in favour.
>
> Thanks.
>
> Mike.
>
My take initial take was to add _np, but after a chat with Joseph's on IRC I
think we should add them as expected names. Florian has raised some concerns.