From: Daniel Jacobowitz <drow@false.org>
To: Richard Stuckey <richard.stuckey@arc.com>
Cc: gdb@sourceware.org
Subject: Re: gdb 6.8 selected_byte_order function
Date: Wed, 24 Sep 2008 13:08:00 -0000 [thread overview]
Message-ID: <20080924130746.GA19429@caradoc.them.org> (raw)
In-Reply-To: <1222253904.3506.12.camel@sad-richards.arc.com>
On Wed, Sep 24, 2008 at 11:58:24AM +0100, Richard Stuckey wrote:
> Given that that the variable âtarget_byte_order_user â holds the userâs
> preference as specified by the âset endianâ command, it seems to me that
> the code should be
>
> if (target_byte_order_user != BFD_ENDIAN_UNKNOWN)
> return target_byte_order_user;
> else
> return gdbarch_byte_order (current_gdbarch);
>
> i.e. if the user has explicitly specified the byte order then we use
> that, otherwise we use the order determined from the current
> architecture.
This happens at a higher level. When the user sets the byte order, we
go through set_endian just below. THe call to gdbarch_update_p
changes current_gdbarch.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-09-24 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 10:59 Richard Stuckey
2008-09-24 13:08 ` Daniel Jacobowitz [this message]
2008-09-24 13:37 ` Richard Stuckey
2008-09-24 13:49 ` Daniel Jacobowitz
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=20080924130746.GA19429@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=richard.stuckey@arc.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