gdb patches to RBS

[Jiri Gaisler]

On 11/14/2014 02:34 AM, Chris Johns wrote:
> On 14/11/2014 9:12 am, Jiri Gaisler wrote:
>>
>> What is the procedure to add gdb patches to RBS?
>>
> 
> Patches are first accepted by the RTEMS Project as the definition of the tools belongs to the project and tool packagers, ie the RSB, need to adopt that definition to get a project tick. Patches should be posted upstream where possible and then referenced from there. If the
> upstream does not have a suitable method to reference patches we can add them to the rtems-tools.git repo under the tools directory. There are specific cases such as the openrisc tools where a specific github instance is referenced as we have a positive undertaking from that
> community the tools are being merged upstream. Examples of upstream patch referencing is qemu and patchworks.
> 
> I do not see a patch management system for gdb. There was talk back in April of this year of gdb using patchworks and then something else however it seems to have died out.
> 
>> I have a few patches that fixes the erc32 simulator and also
>> add support for leon2 and leon3. This would allow us to drop
>> the sis bsp, and also to test the leon2 and leon3 bsp's with
>> sis.
> 
> Excellent. I suggest you provide git patches for the rtems-tools.git repo to add the patches and then provide RSB patches for the sparc gdb build to use them. There are specific sparc patches already present which need updating as they are currently stopping us moving off gdb-7.7.

The latest stable gdb version is 7.8.1, while the git head is at 7.8.50.20141112-cvs .
Should we switch to gdb-7.8.1 or stay at 7.7? It does not really matter to me which
one. The existing sparc gdb patch for 7.7 is merged into my patches as I had to
rework it a bit.

I will try to push my patches upstream to gdb but I suspect it will take
while before the are accepted, as they are quite large.

Jiri.