Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@vnet.ibm.com>
To: Pedro Alves <palves@redhat.com>
Cc: Alan Modra <amodra@gmail.com>,
	Ulrich Weigand <uweigand@de.ibm.com>,
	       gdb-patches@sourceware.org,
	binutils <binutils@sourceware.org>
Subject: Re: [PATCH, RFC] Add support for choosing disassembler cpu in GDB for POWER.
Date: Tue, 11 Oct 2016 18:49:00 -0000	[thread overview]
Message-ID: <8bfd2bd6-c2b3-cf5e-c689-897b877970f1@vnet.ibm.com> (raw)
In-Reply-To: <98f7c932-3347-a07c-5282-ca83cbb89593@redhat.com>

On 10/10/16 7:08 PM, Pedro Alves wrote:
> A command that works for all architectures, like your original
> "set disassembler-cpu" seemingly would be (ignoring implementation
> details).  Maybe "set disassembler-cpu" could be an alias for
> "set $current_arch disassembler-cpu".  GDB would then only need to store
> a disassemble option string for each possible arch, and the alias would just
> need to map the current arch's cpu to the right option string variable.

It doesn't look like set_disassembler_cpu() is passed the gdbarch, so
is there some global variable that it could use to determine what the
current arch is?  That said, even if I do have it, wouldn't we need
to store the set/show commands in the gdbarch so that they can be
called?



> All the information to build this should be in opcodes, I think.  Even
> for "help show disassembler-cpu", it should be possible for gdb to ask
> opcodes to print a description of each possible option,
> since "objdump --help" does it.  Bonus points for hooking that to
> a completer for "set disassembler-cpu <tab>".  :-)

The objdump --help output comes from opcodes/ppc-dis.c's
print_ppc_disassembler_options(FILE *stream).  I actually tried
to call that from show_disassembler_cpu(), but the "file" pointer
it's passed is of type "struct ui_file *file" which looks to be
a black box, so I'm not sure how I can extract a "FILE *" pointer
out of that.

I don't know how to set up a completer and I don't see one.
Do you know of an example in the code I could look at/copy?



> BTW, AFAICS, objdump's -M isn't really only about "cpu".
> "objdump --help" on an --enable-targets=all build of binutils
> shows -M options that are not cpu options.  "set disassembler-options"
> would probably be a better name for this.

I'm fine going with whatever option name people prefer.  If you want
"disassembler-options" instead of just "disassembler", ok, but shouldn't
ARM be renamed then as well if it uses this mechanism?

Peter




  reply	other threads:[~2016-10-11 18:49 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30  2:14 Peter Bergner
2016-09-30 17:55 ` Ulrich Weigand
2016-10-03 20:25   ` Peter Bergner
2016-10-03 22:25     ` Alan Modra
2016-10-06  3:00       ` Peter Bergner
2016-10-06  4:44         ` Alan Modra
2016-10-06  9:52         ` Pedro Alves
2016-10-06 19:26           ` Peter Bergner
2016-10-07 19:21             ` Ulrich Weigand
2016-10-07 21:01               ` Peter Bergner
2016-10-08 14:39                 ` Ulrich Weigand
2016-10-10 23:28               ` Peter Bergner
2016-10-12  8:08                 ` Ulrich Weigand
2016-10-12 10:46                   ` Pedro Alves
2016-10-11  0:09             ` Pedro Alves
2016-10-11 18:49               ` Peter Bergner [this message]
2016-10-12  8:25                 ` Ulrich Weigand
2016-10-27  0:04                   ` Peter Bergner
2016-10-27  9:40                     ` Pedro Alves
2016-10-28 13:47                       ` Peter Bergner
2016-10-28 14:10                         ` Pedro Alves
2016-10-28 14:24                           ` Peter Bergner
2016-10-28 14:30                             ` Pedro Alves
2016-10-28 14:53                               ` Peter Bergner
2016-11-03 11:01                                 ` Pedro Alves
2016-11-03 15:02                                   ` Peter Bergner
2016-11-03 15:06                                     ` Peter Bergner
2016-11-03 16:41                                     ` Ulrich Weigand
2016-11-03 16:49                                       ` Peter Bergner
2016-10-28 12:32                     ` Ulrich Weigand
2016-10-28 13:45                       ` Peter Bergner
2016-10-28 14:15                         ` Ulrich Weigand
2016-10-28 15:02                           ` Peter Bergner
2016-10-28 18:47                             ` Ulrich Weigand
2016-11-02 23:28                               ` Peter Bergner
2016-10-12 19:35                 ` Pedro Alves

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=8bfd2bd6-c2b3-cf5e-c689-897b877970f1@vnet.ibm.com \
    --to=bergner@vnet.ibm.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=uweigand@de.ibm.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