public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: Shaun Jackman <sjackman@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: Disassembling ARM and Thumb code
Date: Mon, 09 May 2005 12:48:00 -0000	[thread overview]
Message-ID: <1115642877.25452.17.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <7f45d939050506093578e17a4b@mail.gmail.com>

On Fri, 2005-05-06 at 17:35, Shaun Jackman wrote:
> On 5/5/05, Daniel Jacobowitz <drow@false.org> wrote:
> > > Hehe. I agree, that's probably not the best plan. However, for the
> > > unique case of 'x/i $pc' it does make a certain amount of sense to use
> > > the CPSR as a hint. I'm not sure if it's worth the special case
> > > though. An explicit switch to the x/i and disas commands to specify
> > > ARM or Thumb dissection is very much a good idea though.
> > 
> > Yes, probably; if you have a good idea for the syntax to use, then
> > maybe we can add it.  I don't much like the idea of target-specific
> > modifiers.
> 
> I like the look of this:
> 
> x/i for intelligent
> x/iw for ARM
> x/ih for Thumb
> 

Ug.  Doesn't really make sense for Thumb-2.  Nor does it make sense for
the 'disassemble' command.

> Another option is...
> 
> set disassembly-flavor arm
> set disassembly-flavor thumb

less objectionable, provided you avoid 'flavor' which is irritating to
those who use British English spelling.

I'd go for 

set disassembly-isa {auto|arm|thumb}

R.

  reply	other threads:[~2005-05-09 12:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06  0:06 Shaun Jackman
2005-05-06  1:56 ` Daniel Jacobowitz
2005-05-06  3:35   ` Shaun Jackman
2005-05-06  4:08     ` Daniel Jacobowitz
2005-05-06 16:35       ` Shaun Jackman
2005-05-09 12:48         ` Richard Earnshaw [this message]
2005-05-09 16:07           ` Shaun Jackman

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=1115642877.25452.17.camel@pc960.cambridge.arm.com \
    --to=rearnsha@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=sjackman@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).