This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Fix CRISv32 compilation
- From: Pedro Alves <palves at redhat dot com>
- To: Ricard Wanderlof <ricard dot wanderlof at axis dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Tue, 03 Sep 2013 13:03:42 +0100
- Subject: Re: [PATCH] Fix CRISv32 compilation
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 00 dot 1308301512140 dot 10770 at lnxricardw dot se dot axis dot com> <5224CAE7 dot 9090309 at redhat dot com> <alpine dot DEB dot 2 dot 00 dot 1309030857010 dot 10770 at lnxricardw dot se dot axis dot com>
On 09/03/2013 08:45 AM, Ricard Wanderlof wrote:
>
> On Mon, 2 Sep 2013, Pedro Alves wrote:
>
>> On 08/30/2013 02:12 PM, Ricard Wanderlof wrote:
>>>
>>> 2013-08-30 Ricard Wanderlof <ricardw@axis.com>
>>>
>>> gdbserver
>>>
>>> * linux-crisv32-low.c: Fix compilation errors.
>>
>> Write:
>>
>> * linux-crisv32-low.c (elf_gregset_t): Delete typedef.
>> (initialize_low_arch): Call init_registers_crisv32 rather than
>> init_register_crisv32.
>>
>> OK with that change.
>
> Ok with me. Thanks for the update. Should I resubmit the patch ?
If there were no changes since the previous post, we just check
it in (and usually reply back saying so). If the patch was approved
with changes, we commit, and reply back saying "this is what I
checked in", showing the final version. Ultimately, what this means
is we always post final version of the patch to the mailing list,
exactly as it went in.
>> (I can't see how the typedef was breaking the build though)
>
> With the typedef left in, I get
...
> when building gdbserver using the target compiler.
Thanks, that's the sort of info that's helpful to have the
in the patch rationale (which ideally ends up in the
commit log).
--
Pedro Alves