[PATCH 00/11] libctf: various portability fixes and small bugfixes

Nick Alcock nick.alcock@oracle.com
Tue Jan 7 17:07:00 GMT 2020


On 19 Dec 2019, Alan Modra outgrape:

> On Mon, Dec 16, 2019 at 10:53:46PM +0000, Nick Alcock wrote:
>> The libiberty and binutils bits outside the first patch in the series have not
>> appeared here before and need review.
>
> The binutils part is fine.  libiberty patches should go to
> gcc-patches@gcc.gnu.org as per libiberty/README.

Oh, thank you, I never noticed this before. I'll split out the
libiberty/include portion and respin things as suggested there (make
maint-deps and make-stamp-functions, etc.)

> binutils/libiberty can be imported from the gcc repo later by anyone
> with write access to the binutils repo.  If the gcc patch approval
> process takes too long then you may apply the patch to binutils.

I guess this means I have to respin this bit against GCC trunk (and keep
the current patch as a necessary-for-testing-but-will-be-dropped
portion if the resulting patch is any different).



More information about the Binutils mailing list