> What would be needed to make this fix acceptable so that OpenOCD would
> have no issues with newer versions of GDB?

I have applied this patch and now the latest openocd master (with this
patch applied) works with Linaro GCC 4.7-2012.4 and Linaro GDB
7.4-2012.4.  I'm not sure at what point gdb switch it's awareness of
the non-existent registers.  From experience, I wasn't able to get any
version of 7.3 or newer to work unless this patch is applied.  If
anybody knows when gdb got rid of these unused registers, it would be
helpful information to be able to design an appropriate OpenOCD patch.

To do this properly, it seems like openocd would have to be aware of
which version of gdb was going to be used with it, and conditionally
compile this file appropriately.  Alternatively, a future release of
OpenOCD could simply require gdb version 7.3 or newer.  Or, perhaps
there is a way to determine the version of gdb at runtime, and act
appropriately?  All of these options have their pros/cons.

>From a maintenance point of view, it seems dropping support for the
older versions of gdb would be the simplest, but this will probably
hurt many people using canned toolchains that have older versions of
gdb.  Then again, maybe those people are using the old releases of
OpenOCD, and aren't keeping up with the git stuff, so this wouldn't
affect most people.  Adding conditional compilation and/or runtime
version checking seems like it could be a can of worms and a potential
maintenance burden, but maybe I'm wrong.

Thoughts?
Luke

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to