This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 1/2] Sync libiberty with gcc upstream
- From: Pedro Alves <palves at redhat dot com>
- To: Iain Buclaw <ibuclaw at gdcproject dot org>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 24 Jun 2015 14:54:10 +0100
- Subject: Re: [PATCH v2 1/2] Sync libiberty with gcc upstream
- Authentication-results: sourceware.org; auth=none
- References: <CABOHX+fRn+jrNs_hfuf6FHr3koC7ynSDYRFfjkFesJYgfUjdjg at mail dot gmail dot com> <558A95CE dot 2060506 at redhat dot com> <CABOHX+cYeXF4vQ+TAhrwrp=yqLKK2zPbUHLbyxobn-2yyD1_2g at mail dot gmail dot com>
On 06/24/2015 02:52 PM, Iain Buclaw wrote:
> On 24 June 2015 at 13:34, Pedro Alves <palves@redhat.com> wrote:
>> On 06/19/2015 04:18 PM, Iain Buclaw wrote:
>>> Belated attempt at downstreaming libiberty changes from upstream.
>>> Split it into two patches, one with dlang related changes, the other
>>> with everything else.
>>>
>>> As requested, commits have been replayed ontop of gdb rather than a
>>> straight diff between the directories.
>>
>> Excellent, thanks.
>>
>> If we regenerate the affected configure files afterwards, do end up
>> with no changes? If so, the two patches are OK.
>>
>
> If by regenerating, you mean by using autoreconf2.64 on the toplevel
> and libiberty directories, then yes no further changes crop up.
Exactly.
>
>> I assume diffing the dirs still comes up empty after these?
>>
>
> Diffing the libiberty directory between gcc and gdb comes up empty
> after these, yes.
Awesome. Many thanks for doing all this. Much appreciated.
--
Pedro Alves