This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: The 2.20 release code freeze is very near
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Roland McGrath <roland at hack dot frob dot com>, Allan McRae <allan at archlinux dot org>
- Cc: libc-alpha <libc-alpha at sourceware dot org>
- Date: Wed, 02 Jul 2014 19:42:03 -0400
- Subject: Re: The 2.20 release code freeze is very near
- Authentication-results: sourceware.org; auth=none
- References: <53B3D952 dot 6090906 at archlinux dot org> <20140702165555 dot F29192C397B at topped-with-meat dot com>
On 07/02/2014 12:55 PM, Roland McGrath wrote:
> I think it makes sense to say that we are now in a "slushy freeze".
Agreed.
>> Can I also get a status on these so I can track where we are:
>> 1) -Wundef cleanup
>
> Siddhesh and Andreas mentioned many outstanding cases. Nobody has
> mentioned IS_IN_*/NOT_IN_*, which I also see. I have some vague notions
> of attacking the IS_IN*/NOT_IN_* cases in a holistic way, but I have not
> put actual effort into it.
I'm scared of the IS_IN*/NOT_IN_* changes, but you're right in that you
can verify that nothing broke because of them.
>> 2) De-add-on-ification of NPTL
> Carlos just needs to get on the stick, or else hppa can be broken IMHO.
> For ia64, I'm sure everybody will be happy if anybody who feels
> competent to review and test ia64 changes does so. rth has indicated he
> might be able to do it, but he's not obliged to.
I'm still on it, I did the hppa ABI baselines first to make sure that
nothing broke and so that debian and gentoo can see if anything does
break. The distros apply some weird patches and I can't always hold
their hands.
> But so far people have not been jumping up to do it, so
> I'm not sure anyone will without just forcing them by committing.
That was the case with pthread_once unification also :-)
> So here's my tentative plan: I hope Carlos will deal with hppa between
> now and Tuesday. I hope rth or someone will deal with ia64 soon.
> Whether they do or not, I'll repost the roland/nptl branch changes next
> week (after fresh x86 and ARM testing). Then, unless someone has
> concrete review feedback or does testing that turns up problems and
> those are not all resolved quickly, I'll commit by the end of the week.
> If hppa and/or ia64 are still lagging, their builds will almost
> certainly be broken and that's their problem. If other machines haven't
> even attempted the testing, then their builds might be broken (though I
> hope not) and if so that's their problem.
I should have things fixed. Despite it being my brother's wedding the
days off mean I get to hack on upstream to my heart's content.
Cheers,
Carlos.