From: Andrew Cagney <ac131313@redhat.com>
To: Richard.Earnshaw@arm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH ARM add new set/show arm commands
Date: Mon, 24 Mar 2003 17:10:00 -0000 [thread overview]
Message-ID: <3E7F3C13.5080708@redhat.com> (raw)
In-Reply-To: <200303240947.h2O9lEZ29462@pc960.cambridge.arm.com>
> This patch starts the process of moving the arm-specific set/show options
>> > into a sub-group. For the moment I've only done this for the set/show
>> > disassembly-flavor command, where I've also taken the opportunity to drop
>> > "flavor" from the command (it's non-intuitive if you speak English-English
>> > :-)
>
>>
>> See: set [<arch>?] disassembler, replace disassembly-flavour or flavor[sic]
>> http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=548
>>
>> enjoy,
>> Andrew
>>
>>
>
>> > So we now have
>> >
>> > set arm disassembly
>> >
>> > and
>> >
>> > show arm disassembly
>
>
> Are you suggesting I should change the option name to "set arm
> disassembler"? If so, I've no problem with that. If not, what are you
Yes, just "set arm disassembler". Er, actually, is "set arm
disassembler-options" better? Either name is more in line with the
existing objdump --disassembler-options option.
Andrew
> suggesting? Currently ARM does not support a "set arm architecture",
> though it might be needed for supporting interworking binaries and calls
> to functions from gdb.
>
> R.
>
>
next prev parent reply other threads:[~2003-03-24 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 16:29 Richard Earnshaw
2003-03-22 22:20 ` Andrew Cagney
2003-03-24 9:48 ` Richard Earnshaw
2003-03-24 17:10 ` Andrew Cagney [this message]
2003-03-25 12:24 ` Richard Earnshaw
2003-03-25 15:19 ` Andrew Cagney
2003-03-25 15:37 ` Richard Earnshaw
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=3E7F3C13.5080708@redhat.com \
--to=ac131313@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--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