Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Shaun Jackman <sjackman@gmail.com>
To: gdb@sources.redhat.com
Subject: Re: Disassembling ARM and Thumb code
Date: Mon, 09 May 2005 16:07:00 -0000	[thread overview]
Message-ID: <7f45d939050509090776da6c@mail.gmail.com> (raw)
In-Reply-To: <1115642877.25452.17.camel@pc960.cambridge.arm.com>

On 5/9/05, Richard Earnshaw <rearnsha@gcc.gnu.org> wrote:
> On Fri, 2005-05-06 at 17:35, Shaun Jackman wrote:
> > 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.

x/ia for ARM/Thumb-2 and x/it for Thumb then. Even with a 'set ...
{arm, thumb}' command, a quick-to-type and
quick-override-of-the-default x/i style command is useful.

> > 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.

I agree entirely, but I'd guess that disassembly-flavor has been
around for a while. Should the previous spelling be deprecated?

objdump already has a name for this option:
	set disassembler-options {intel, att, force-thumb, ...}
I'd prefer simply `thumb' to `force-thumb', but parallelism between
tools is a healthy goal.

Cheers,
Shaun


      reply	other threads:[~2005-05-09 16:07 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
2005-05-09 16:07           ` Shaun Jackman [this message]

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=7f45d939050509090776da6c@mail.gmail.com \
    --to=sjackman@gmail.com \
    --cc=gdb@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