Re: [PATCH v3 2/8] gdb-cross: avoid tune specific paths

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Tue, 2017-04-11 at 10:16 -0500, Mark Hatle wrote:
> On 4/11/17 9:56 AM, Patrick Ohly wrote:
> > 
> > gdb-cross used to be specific to the tune flags, but isn't
> > anymore. Therefore it is enough to use TARGET_SYS instead of
> > TUNE_PKGARCH to create a unique path.
> Are you sure about this.  On non-intel architectures, it used to be
> VERY common
> that the specific instruction set for a process was programmed into
> gdb.
> 
> Sometimes the user could (after loading gdb) change the instructions,
> but this
> was an aweful user experience.
> 
> Good example of this would be Power, e500, etc.  The instruction sets
> are not
> actually compatible with each other, so GDB needs to know the
> specific
> instruction in order to work.

This may or may not be an issue with gdb however I'd note that we only
build one gdb-cross regardless, we don't configure it with any target
tune specifics and the gdb we build for the sdk is built similarly. So
if it is an issue, its not one we've had reported to us and we don't
configure gdb in any target specific way so this patch should be
safe...

Cheers,

Richard