[v3,0/6] The remaining x86_64-gnu patches

  These are the patches that I have locally that have not (yet) been
pushed. Most of them I have already sent previously, but have made
changes to since then. Please see the notes on individual patches.

I'm putting "v3" on the whole series because some of the patches here
have already been through v1 and v2.

If these patches are pushed, it should be possible for anyone to build
x86_64-gnu glibc just out of Git master, without having to dig through
the mailing list archive for uncommited patches.

Sergey
  

On Sat, 29 Apr 2023, Sergey Bugaev via Libc-alpha wrote:

> If these patches are pushed, it should be possible for anyone to build
> x86_64-gnu glibc just out of Git master, without having to dig through
> the mailing list archive for uncommited patches.

In that case I think there should be a patch to build-many-glibcs.py to 
add an x86_64-gnu configuration, as well as updates to NEWS and README to 
reflect the new support for such a configuration.
  

Hello,

On Tue, May 2, 2023 at 5:03 PM Joseph Myers <joseph@codesourcery.com> wrote:
> On Sat, 29 Apr 2023, Sergey Bugaev via Libc-alpha wrote:
>
> > If these patches are pushed, it should be possible for anyone to build
> > x86_64-gnu glibc just out of Git master, without having to dig through
> > the mailing list archive for uncommited patches.
>
> In that case I think there should be a patch to build-many-glibcs.py to
> add an x86_64-gnu configuration, as well as updates to NEWS and README to
> reflect the new support for such a configuration.

yes, that would be great!

It would also probably make sense to mention my other changes, of
which there have been many, in the NEWS (would a simple "many fixes
and improvements in the Hurd port" suffice?)

Am I supposed to write a patch for this, or will somebody else do it?

Will adding it to build-many-glibcs.py automatically enable some sort
of server-side CI for this configuration?

Sergey
  

Joseph Myers, le mar. 02 mai 2023 14:03:16 +0000, a ecrit:
> On Sat, 29 Apr 2023, Sergey Bugaev via Libc-alpha wrote:
> 
> > If these patches are pushed, it should be possible for anyone to build
> > x86_64-gnu glibc just out of Git master, without having to dig through
> > the mailing list archive for uncommited patches.
> 
> In that case I think there should be a patch to build-many-glibcs.py to 
> add an x86_64-gnu configuration,

I have it pending, just waiting for gcc 13.

Samuel
  

On Tue, 2 May 2023, Samuel Thibault via Libc-alpha wrote:

> Joseph Myers, le mar. 02 mai 2023 14:03:16 +0000, a ecrit:
> > On Sat, 29 Apr 2023, Sergey Bugaev via Libc-alpha wrote:
> > 
> > > If these patches are pushed, it should be possible for anyone to build
> > > x86_64-gnu glibc just out of Git master, without having to dig through
> > > the mailing list archive for uncommited patches.
> > 
> > In that case I think there should be a patch to build-many-glibcs.py to 
> > add an x86_64-gnu configuration,
> 
> I have it pending, just waiting for gcc 13.

It's enough for the x86_64-gnu support to be in GCC mainline when the 
patch to build-many-glibcs.py goes in; it doesn't need to be in the 
release branch (though being in the release branch may be helpful for 
users).
  

On Tue, 2 May 2023, Sergey Bugaev via Libc-alpha wrote:

> It would also probably make sense to mention my other changes, of
> which there have been many, in the NEWS (would a simple "many fixes
> and improvements in the Hurd port" suffice?)

That may well be an appropriate way to describe them (if you haven't 
opened individual bug reports in Bugzilla; if a bug is reported in 
Bugzilla, then marked FIXED after the commit with the target milestone set 
to the first mainline release with the fix, it will automatically be 
listed in the list of fixed bugs in NEWS).

> Am I supposed to write a patch for this, or will somebody else do it?

The general expectation is that someone adding a significant new feature 
also does the NEWS update, and someone adding a new ABI does the 
build-many-glibcs.py update.

> Will adding it to build-many-glibcs.py automatically enable some sort
> of server-side CI for this configuration?

My build-many-glibcs.py bots automatically run the compilation parts of 
the testsuite for all configurations included in that script.