Re: 2.31: < 2 weeks to go

[Joseph Myers <joseph@codesourcery.com>]

On Sun, 22 Dec 2019, Siddhesh Poyarekar wrote:

> > What should we do about the built-in system call tables?  I think it's
> > desirable to have this in the release to get a well-defined system call
> > profile after the the Y2038 changes.  Otherwise, there will be a lot of
> > variance regarding the system calls glibc makes depending on which
> > version of the kernel headers glibc was built with.
> > 
> >   <https://sourceware.org/ml/libc-alpha/2019-12/msg00567.html>
> > 
> > The actual code changes (the first two patches) could go in before the
> > build-many-glibcs.py changes have been reviewed.  I think the updating
> > logic now follows Joseph's suggestion, but I don't know if the changes I
> > did on build-many-glibcs.py are acceptable from a consistency/style
> > perspective.
> 
> I took a quick look at the patches and the discussions earlier and it
> looked to me like they're headed in the right direction.  Joseph, do you
> agree?  If you don't have the bandwidth to do a full review, I can help
> with that.

The general approach seems plausible.  I don't expect much time for patch 
review while working on the GCC git conversion.

-- 
Joseph S. Myers
joseph@codesourcery.com