Re: Syncing the toplevel with the GCC tree

[Alan Modra <amodra@gmail.com>]

On Wed, Jul 26, 2023 at 03:47:55PM +0200, Arsen Arsenović via Binutils wrote:
> Hi there!
> 
> I'm currently in the process of replacing the out-of-date in-tree intl
> with an out-of-tree gettext.  This requires modification to both the
> binutils-gdb and gcc repositories, and I've noticed that some changes in
> the latter haven't propagated to binutils-gdb yet.
> 
> How does the process of syncing these trees up work?

It's painful and not something I'm going to do again.  Last time I did
so I managed to break binutils-gdb.

The process goes like this:
1) Some ports have been removed from gcc but not binutils-gdb, so
firstly revert those patches to the top-level on the gcc side.

2) Copy over the gcc configury and makefiles.

3) Reapply binutils patches that haven't been applied to gcc, either
because the people making the patches didn't care enough to submit
them to gcc, or because the gcc maintainers didn't care enough to ack
those patches.

This was the list I used last time.  Very likely it needs updating.

Revert gcc
dc832fb39fc0 2022-08-25
fc259b522c0f 2022-06-25

Reapply binutils
69961a84c9b3 2018-12-12
50ad1254d503 2021-01-09
bb368aad297f 2022-03-11
de83289ef32e 2022-04-08
e5f2f7d901ee 2022-07-26
2cac01e3ffff 2022-09-26


> I intend on synchronizing the toplevels and emailing in patches that
> allow using modern gettext to all the relevant maintainers after some
> further testing.
> 
> It would also be good to synchronize ahead of the 2.41 release of
> Binutils.
> 
> Thanks in advance, have a lovely day.
> -- 
> Arsen Arsenović



-- 
Alan Modra
Australia Development Lab, IBM