This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [PATCH 00/11] libctf: various portability fixes and small bugfixes
- From: Nick Alcock <nick dot alcock at oracle dot com>
- To: Alan Modra <amodra at gmail dot com>
- Cc: binutils at sourceware dot org, indu dot bhagat at oracle dot com, jose dot marchesi at oracle dot com
- Date: Tue, 07 Jan 2020 17:04:39 +0000
- Subject: Re: [PATCH 00/11] libctf: various portability fixes and small bugfixes
- References: <20191216225357.87247-1-nick.alcock@oracle.com> <20191219005232.GA32672@bubble.grove.modra.org>
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).