Re: [RFA:] sim-config.c: When having a bfd, don't just checkbfd_little_endian

[Paul Schlie <schlie at comcast dot net>]

> Hans-Peter Nilsson wrote:
>
> That is, we try and run a binary file with a specified
> architecture and test output as with the ELF.  Current behavior
> is to emit:
>
> Target (LITTLE_ENDIAN) and specified (BIG_ENDIAN) byte order in conflict
> 0
> 0
> 4
> 42
>
> which is clearly wrong; BIG_ENDIAN isn't *specified* neither
> should it be perceived as such for a binary file.

Unless I misunderstand, the protocol should be endian neutral; as such
should likely default to big-endian just like the the rest of gdb's
serial protocol, and networking in general. (arguably there's shouldn't be
any reason for gdb itself be target encoding dependant, correspondingly all
targets should expect the same, and encode/decode appropriately from/to
their respective endian preference/requirements, I would think?)