2.33 Slush freeze set to 01/11

Adhemerval Zanella adhemerval.zanella@linaro.org
Wed Jan 6 13:55:02 GMT 2021



On 06/01/2021 10:36, H.J. Lu wrote:
> On Wed, Jan 6, 2021 at 4:57 AM Adhemerval Zanella
> <adhemerval.zanella@linaro.org> wrote:
>>
>> Hi all,
>>
>> As we discussed on last Monday call, the plan is to start slush freeze
>> at next Monday 01/11.  The idea is no new features should be in besides
>> the ones listed and discussed on the release blockers for 2.33 [1].
>>
>> On the release blockers I see three upcoming features that we need
>> to review:
>>
>>   1 x86 patches to implement the support for ISA level.
>>     - x86: Support GNU_PROPERTY_X86_ISA_1_V[234] marker [BZ #26717]
>>     - x86: Move x86 processor cache info to cpu_features
>>     - ldconfig/x86: Store ISA level in cache and aux cache
>>
>>   2. ld.so: DSO sorting algorithm patch, both testing infrastructure
>>      and new algorithm [BZ #17645].
>>
>>   3. riscv: ifunc support
>>
>> For 1. I have started to review those and I think base on last reviews
>> the design should be regarding the ld.so cache. Florian said that he
>> will also help on this one.
>>
>> Carlos, how is 2. review going? I kind afraid this is a very intrusive
>> change and I am not sure if we should aim for 2.33, although I give
>> that this is long standing issue and we have reports that users has
>> been deployed in large environments. Should we aim for 2.33 or push
>> it for initial 2.34 development?
>>
>> DJ, how is 3 review going? I think this is sensible support since
>> gcc and binutils has been upstream.
>>
>>
>> Beside the new features, we also have important bugfixes but I think
>> they should be easier to integrate on slush freeze:
>>
>>   1. posix: Sync tempname with gnulib (BZ #26648)
>>   2. linux: mips: Fix getdents64 fallback on mips64-n32
>>   3. posix: Fix return value of system if shell can not be executed
>>   4. GCC 11 incompatibilities
>>
>> Of these, I am more worried about the 4. since on release page there is
>> clear indication of the required work on glibc side. I will trigger a
>> gcc11 build check for all architecture to check current status.
>>
>> [1] https://sourceware.org/glibc/wiki/Release/2.33
> 
> We should also fix:
> 
> https://sourceware.org/bugzilla/show_bug.cgi?id=27104
> 

I updated the release wiki with bug and the patch.


More information about the Libc-alpha mailing list