* 2.33 Hard Freeze
@ 2021-01-26 12:18 Adhemerval Zanella
2021-01-26 13:36 ` Szabolcs Nagy
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Adhemerval Zanella @ 2021-01-26 12:18 UTC (permalink / raw)
To: GNU C Library
Hi all,
Now that we handled all the release blockers [1], the master branch
is now at hard freeze. The plan is still to set the release to next
week, Feb 1st (or maybe a couple days later).
As usual, please do not push anything into master and if something
needs to go urgently please cc me with an explanation of why the fix
is necessary (broken build due a glibc issue, 0-day sev-1 security issue,
very important bugfix, etc.).
Currently we have status report for ARC, ARM (hard-float), C-SKY, MIPS
(LE hard-float and BE soft-float), PowerPC (32-bt soft-float, RISC-V
(rv64imac/lp64 and rv64imafdc/lp64) and x86. I will try to get results
for alpha, hppa, sh, and sparc.
Regarding the current issues:
- nios2 is failing to build with GCC11 [2]. From the bug report [3]
it seems to be a binutils issues so I don't consider this a release
blocker.
- There are a couple of GCC11 regressions/blockers [4] [5]. For former
it does seem a to be a gcc regression, while for later I think we
should defer to next release.
- The cond-var issue [6]. Carlos is reviewing it, although I do think
this is kind late for a quite intrusive patchset. I think it would
be better to backport it once we it set to upstream.
[1] https://sourceware.org/glibc/wiki/Release/2.33
[2] https://sourceware.org/pipermail/libc-alpha/2021-January/121936.html
[3] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97683
[4] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98512
[5] https://sourceware.org/pipermail/libc-alpha/2020-December/120560.html
[6] https://patchwork.sourceware.org/project/glibc/list/?series=1496
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 2.33 Hard Freeze
2021-01-26 12:18 2.33 Hard Freeze Adhemerval Zanella
@ 2021-01-26 13:36 ` Szabolcs Nagy
2021-01-26 17:11 ` Adhemerval Zanella
2021-01-26 15:52 ` DJ Delorie
2021-01-27 12:32 ` H.J. Lu
2 siblings, 1 reply; 9+ messages in thread
From: Szabolcs Nagy @ 2021-01-26 13:36 UTC (permalink / raw)
To: Adhemerval Zanella; +Cc: GNU C Library
The 01/26/2021 09:18, Adhemerval Zanella via Libc-alpha wrote:
> Hi all,
>
> Now that we handled all the release blockers [1], the master branch
> is now at hard freeze. The plan is still to set the release to next
> week, Feb 1st (or maybe a couple days later).
>
> As usual, please do not push anything into master and if something
> needs to go urgently please cc me with an explanation of why the fix
> is necessary (broken build due a glibc issue, 0-day sev-1 security issue,
> very important bugfix, etc.).
>
> Currently we have status report for ARC, ARM (hard-float), C-SKY, MIPS
> (LE hard-float and BE soft-float), PowerPC (32-bt soft-float, RISC-V
> (rv64imac/lp64 and rv64imafdc/lp64) and x86. I will try to get results
> for alpha, hppa, sh, and sparc.
>
> Regarding the current issues:
>
> - nios2 is failing to build with GCC11 [2]. From the bug report [3]
> it seems to be a binutils issues so I don't consider this a release
> blocker.
>
> - There are a couple of GCC11 regressions/blockers [4] [5]. For former
> it does seem a to be a gcc regression, while for later I think we
> should defer to next release.
>
> - The cond-var issue [6]. Carlos is reviewing it, although I do think
> this is kind late for a quite intrusive patchset. I think it would
> be better to backport it once we it set to upstream.
well there is a regression i could not reproduce yet:
https://sourceware.org/bugzilla/show_bug.cgi?id=27237
https://sourceware.org/pipermail/libc-alpha/2021-January/121916.html
the problematic patch can be reverted (it's not needed
for correctness) but i would like to understand what's
going on.
>
> [1] https://sourceware.org/glibc/wiki/Release/2.33
> [2] https://sourceware.org/pipermail/libc-alpha/2021-January/121936.html
> [3] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97683
> [4] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98512
> [5] https://sourceware.org/pipermail/libc-alpha/2020-December/120560.html
> [6] https://patchwork.sourceware.org/project/glibc/list/?series=1496
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 2.33 Hard Freeze
2021-01-26 13:36 ` Szabolcs Nagy
@ 2021-01-26 17:11 ` Adhemerval Zanella
2021-01-26 18:30 ` Szabolcs Nagy
0 siblings, 1 reply; 9+ messages in thread
From: Adhemerval Zanella @ 2021-01-26 17:11 UTC (permalink / raw)
To: Szabolcs Nagy; +Cc: GNU C Library
On 26/01/2021 10:36, Szabolcs Nagy wrote:
> The 01/26/2021 09:18, Adhemerval Zanella via Libc-alpha wrote:
>> Hi all,
>>
>> Now that we handled all the release blockers [1], the master branch
>> is now at hard freeze. The plan is still to set the release to next
>> week, Feb 1st (or maybe a couple days later).
>>
>> As usual, please do not push anything into master and if something
>> needs to go urgently please cc me with an explanation of why the fix
>> is necessary (broken build due a glibc issue, 0-day sev-1 security issue,
>> very important bugfix, etc.).
>>
>> Currently we have status report for ARC, ARM (hard-float), C-SKY, MIPS
>> (LE hard-float and BE soft-float), PowerPC (32-bt soft-float, RISC-V
>> (rv64imac/lp64 and rv64imafdc/lp64) and x86. I will try to get results
>> for alpha, hppa, sh, and sparc.
>>
>> Regarding the current issues:
>>
>> - nios2 is failing to build with GCC11 [2]. From the bug report [3]
>> it seems to be a binutils issues so I don't consider this a release
>> blocker.
>>
>> - There are a couple of GCC11 regressions/blockers [4] [5]. For former
>> it does seem a to be a gcc regression, while for later I think we
>> should defer to next release.
>>
>> - The cond-var issue [6]. Carlos is reviewing it, although I do think
>> this is kind late for a quite intrusive patchset. I think it would
>> be better to backport it once we it set to upstream.
>
>
> well there is a regression i could not reproduce yet:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=27237
> https://sourceware.org/pipermail/libc-alpha/2021-January/121916.html
>
> the problematic patch can be reverted (it's not needed
> for correctness) but i would like to understand what's
> going on.
I am not sure about this one, I am trying to replicate it on a powerpc
with the same build logs from the reported issue but I couldn't.
I even tried to run the tests contiguously for some time, but I couldn't
hit the issue.
From you analysis it does not really seems related, thoughts?
>
>>
>> [1] https://sourceware.org/glibc/wiki/Release/2.33
>> [2] https://sourceware.org/pipermail/libc-alpha/2021-January/121936.html
>> [3] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97683
>> [4] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98512
>> [5] https://sourceware.org/pipermail/libc-alpha/2020-December/120560.html
>> [6] https://patchwork.sourceware.org/project/glibc/list/?series=1496
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 2.33 Hard Freeze
2021-01-26 17:11 ` Adhemerval Zanella
@ 2021-01-26 18:30 ` Szabolcs Nagy
2021-01-26 19:49 ` Adhemerval Zanella
0 siblings, 1 reply; 9+ messages in thread
From: Szabolcs Nagy @ 2021-01-26 18:30 UTC (permalink / raw)
To: Adhemerval Zanella; +Cc: GNU C Library
The 01/26/2021 14:11, Adhemerval Zanella wrote:
> On 26/01/2021 10:36, Szabolcs Nagy wrote:
> > The 01/26/2021 09:18, Adhemerval Zanella via Libc-alpha wrote:
> >> Hi all,
> >>
> >> Now that we handled all the release blockers [1], the master branch
> >> is now at hard freeze. The plan is still to set the release to next
> >> week, Feb 1st (or maybe a couple days later).
> >>
> >> As usual, please do not push anything into master and if something
> >> needs to go urgently please cc me with an explanation of why the fix
> >> is necessary (broken build due a glibc issue, 0-day sev-1 security issue,
> >> very important bugfix, etc.).
> >>
> >> Currently we have status report for ARC, ARM (hard-float), C-SKY, MIPS
> >> (LE hard-float and BE soft-float), PowerPC (32-bt soft-float, RISC-V
> >> (rv64imac/lp64 and rv64imafdc/lp64) and x86. I will try to get results
> >> for alpha, hppa, sh, and sparc.
> >>
> >> Regarding the current issues:
> >>
> >> - nios2 is failing to build with GCC11 [2]. From the bug report [3]
> >> it seems to be a binutils issues so I don't consider this a release
> >> blocker.
> >>
> >> - There are a couple of GCC11 regressions/blockers [4] [5]. For former
> >> it does seem a to be a gcc regression, while for later I think we
> >> should defer to next release.
> >>
> >> - The cond-var issue [6]. Carlos is reviewing it, although I do think
> >> this is kind late for a quite intrusive patchset. I think it would
> >> be better to backport it once we it set to upstream.
> >
> >
> > well there is a regression i could not reproduce yet:
> >
> > https://sourceware.org/bugzilla/show_bug.cgi?id=27237
> > https://sourceware.org/pipermail/libc-alpha/2021-January/121916.html
> >
> > the problematic patch can be reverted (it's not needed
> > for correctness) but i would like to understand what's
> > going on.
>
> I am not sure about this one, I am trying to replicate it on a powerpc
> with the same build logs from the reported issue but I couldn't.
> I even tried to run the tests contiguously for some time, but I couldn't
> hit the issue.
>
> From you analysis it does not really seems related, thoughts?
i cant reproduce this either but i noticed that some
tests run with -DMODULE_NAME=libc for some reason:
test-mutexattr-printers.c
test-mutex-printers.c
test-condattr-printers.c
test-cond-printers.c
test-rwlockattr-printers.c
test-rwlock-printers.c
../sysdeps/unix/sysv/linux/tst-sysconf-iov_max-uapi.c
which can cause problem (though not related to the
particular reported issue).
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 2.33 Hard Freeze
2021-01-26 18:30 ` Szabolcs Nagy
@ 2021-01-26 19:49 ` Adhemerval Zanella
0 siblings, 0 replies; 9+ messages in thread
From: Adhemerval Zanella @ 2021-01-26 19:49 UTC (permalink / raw)
To: Szabolcs Nagy; +Cc: GNU C Library
On 26/01/2021 15:30, Szabolcs Nagy wrote:
> The 01/26/2021 14:11, Adhemerval Zanella wrote:
>> On 26/01/2021 10:36, Szabolcs Nagy wrote:
>>> The 01/26/2021 09:18, Adhemerval Zanella via Libc-alpha wrote:
>>>> Hi all,
>>>>
>>>> Now that we handled all the release blockers [1], the master branch
>>>> is now at hard freeze. The plan is still to set the release to next
>>>> week, Feb 1st (or maybe a couple days later).
>>>>
>>>> As usual, please do not push anything into master and if something
>>>> needs to go urgently please cc me with an explanation of why the fix
>>>> is necessary (broken build due a glibc issue, 0-day sev-1 security issue,
>>>> very important bugfix, etc.).
>>>>
>>>> Currently we have status report for ARC, ARM (hard-float), C-SKY, MIPS
>>>> (LE hard-float and BE soft-float), PowerPC (32-bt soft-float, RISC-V
>>>> (rv64imac/lp64 and rv64imafdc/lp64) and x86. I will try to get results
>>>> for alpha, hppa, sh, and sparc.
>>>>
>>>> Regarding the current issues:
>>>>
>>>> - nios2 is failing to build with GCC11 [2]. From the bug report [3]
>>>> it seems to be a binutils issues so I don't consider this a release
>>>> blocker.
>>>>
>>>> - There are a couple of GCC11 regressions/blockers [4] [5]. For former
>>>> it does seem a to be a gcc regression, while for later I think we
>>>> should defer to next release.
>>>>
>>>> - The cond-var issue [6]. Carlos is reviewing it, although I do think
>>>> this is kind late for a quite intrusive patchset. I think it would
>>>> be better to backport it once we it set to upstream.
>>>
>>>
>>> well there is a regression i could not reproduce yet:
>>>
>>> https://sourceware.org/bugzilla/show_bug.cgi?id=27237
>>> https://sourceware.org/pipermail/libc-alpha/2021-January/121916.html
>>>
>>> the problematic patch can be reverted (it's not needed
>>> for correctness) but i would like to understand what's
>>> going on.
>>
>> I am not sure about this one, I am trying to replicate it on a powerpc
>> with the same build logs from the reported issue but I couldn't.
>> I even tried to run the tests contiguously for some time, but I couldn't
>> hit the issue.
>>
>> From you analysis it does not really seems related, thoughts?
>
> i cant reproduce this either but i noticed that some
> tests run with -DMODULE_NAME=libc for some reason:
>
> test-mutexattr-printers.c
> test-mutex-printers.c
> test-condattr-printers.c
> test-cond-printers.c
> test-rwlockattr-printers.c
> test-rwlock-printers.c
> ../sysdeps/unix/sysv/linux/tst-sysconf-iov_max-uapi.c
>
> which can cause problem (though not related to the
> particular reported issue).
>
From BZ#27237 [1] report it seems it would be better to revert
this last patch and check if we can re-enable on 2.34 once we
fix the regression.
[1] https://sourceware.org/bugzilla/show_bug.cgi?id=27237
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 2.33 Hard Freeze
2021-01-26 12:18 2.33 Hard Freeze Adhemerval Zanella
2021-01-26 13:36 ` Szabolcs Nagy
@ 2021-01-26 15:52 ` DJ Delorie
2021-01-26 17:09 ` Adhemerval Zanella
2021-01-27 12:32 ` H.J. Lu
2 siblings, 1 reply; 9+ messages in thread
From: DJ Delorie @ 2021-01-26 15:52 UTC (permalink / raw)
To: Adhemerval Zanella; +Cc: libc-alpha
Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org> writes:
> As usual, please do not push anything into master and if something
> needs to go urgently please cc me with an explanation of why the fix
> is necessary (broken build due a glibc issue, 0-day sev-1 security issue,
> very important bugfix, etc.).
I would like to get my nsswitch disable-reloading patch in as it's tiny
and a security issue:
https://sourceware.org/pipermail/libc-alpha/2021-January/121958.html
https://sourceware.org/pipermail/libc-alpha/2021-January/122023.html
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: 2.33 Hard Freeze
2021-01-26 12:18 2.33 Hard Freeze Adhemerval Zanella
2021-01-26 13:36 ` Szabolcs Nagy
2021-01-26 15:52 ` DJ Delorie
@ 2021-01-27 12:32 ` H.J. Lu
2 siblings, 0 replies; 9+ messages in thread
From: H.J. Lu @ 2021-01-27 12:32 UTC (permalink / raw)
To: Adhemerval Zanella; +Cc: GNU C Library
On Tue, Jan 26, 2021 at 4:46 AM Adhemerval Zanella via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> Hi all,
>
> Now that we handled all the release blockers [1], the master branch
> is now at hard freeze. The plan is still to set the release to next
> week, Feb 1st (or maybe a couple days later).
>
> As usual, please do not push anything into master and if something
> needs to go urgently please cc me with an explanation of why the fix
> is necessary (broken build due a glibc issue, 0-day sev-1 security issue,
> very important bugfix, etc.).
>
> Currently we have status report for ARC, ARM (hard-float), C-SKY, MIPS
> (LE hard-float and BE soft-float), PowerPC (32-bt soft-float, RISC-V
> (rv64imac/lp64 and rv64imafdc/lp64) and x86. I will try to get results
> for alpha, hppa, sh, and sparc.
>
> Regarding the current issues:
>
> - nios2 is failing to build with GCC11 [2]. From the bug report [3]
> it seems to be a binutils issues so I don't consider this a release
> blocker.
>
> - There are a couple of GCC11 regressions/blockers [4] [5]. For former
> it does seem a to be a gcc regression, while for later I think we
> should defer to next release.
>
> - The cond-var issue [6]. Carlos is reviewing it, although I do think
> this is kind late for a quite intrusive patchset. I think it would
> be better to backport it once we it set to upstream.
>
> [1] https://sourceware.org/glibc/wiki/Release/2.33
> [2] https://sourceware.org/pipermail/libc-alpha/2021-January/121936.html
> [3] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97683
> [4] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98512
> [5] https://sourceware.org/pipermail/libc-alpha/2020-December/120560.html
> [6] https://patchwork.sourceware.org/project/glibc/list/?series=1496
I discovered a 2.33 regression:
https://sourceware.org/bugzilla/show_bug.cgi?id=26625
A patch is posted at
https://sourceware.org/pipermail/binutils/2021-January/115088.html
It should be fixed before 2.33 is released.
--
H.J.
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2021-01-27 18:44 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-26 12:18 2.33 Hard Freeze Adhemerval Zanella
2021-01-26 13:36 ` Szabolcs Nagy
2021-01-26 17:11 ` Adhemerval Zanella
2021-01-26 18:30 ` Szabolcs Nagy
2021-01-26 19:49 ` Adhemerval Zanella
2021-01-26 15:52 ` DJ Delorie
2021-01-26 17:09 ` Adhemerval Zanella
2021-01-27 18:44 ` DJ Delorie
2021-01-27 12:32 ` H.J. Lu
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).