From: Paul Schlie <schlie@comcast.net>
To: <gdb-patches@sources.redhat.com>
Subject: Re: [RFA:] sim-config.c: When having a bfd, don't just check bfd_little_endian
Date: Wed, 10 Nov 2004 19:01:00 -0000 [thread overview]
Message-ID: <BDB7CFCB.7E5E%schlie@comcast.net> (raw)
> 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?)
next reply other threads:[~2004-11-10 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 19:01 Paul Schlie [this message]
2004-11-10 19:12 ` Paul Schlie
-- strict thread matches above, loose matches on Subject: below --
2004-11-09 22:02 Hans-Peter Nilsson
2004-11-10 15:13 ` Andrew Cagney
2004-11-16 7:19 ` Hans-Peter Nilsson
2004-11-16 16:16 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BDB7CFCB.7E5E%schlie@comcast.net \
--to=schlie@comcast.net \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox