From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: bergner@vnet.ibm.com (Peter Bergner)
Cc: amodra@gmail.com (Alan Modra),
gdb-patches@sourceware.org,
binutils@sourceware.org (binutils)
Subject: Re: [PATCH, RFC] Add support for choosing disassembler cpu in GDB for POWER.
Date: Fri, 30 Sep 2016 17:55:00 -0000 [thread overview]
Message-ID: <20160930161908.6A43511C24D@oc8523832656.ibm.com> (raw)
In-Reply-To: <70c7efa4-c47e-6afc-9572-f23e2dd852e4@vnet.ibm.com> from "Peter Bergner" at Sep 29, 2016 08:40:30 PM
Peter Bergner wrote:
> This patch adds the new GDB commands "set disassembler-cpu <CPU>" and
> "show disassembler-cpu". It also splits the one huge GDB test case into
> multiple test cases without the unneeded file offsets.
>
> Alan and Uli, does this patch look like something we'd like? If we do want
> this, what do you think of the "disassembler-cpu" command name? Is there
> something better to use? Thoughts?
I agree that this looks like a feature that would be nice to have.
The implementation in the patch does appear to be a bit ad-hoc, however :-)
Why would we want to pass that information via a new global variable, if
there is already an element "disassembler_options" in the struct
disassemble_info that GDB passes to bfd? See e.g. i386_print_insn.
I'm also not really happy about the tight integration of opcode/ppc.h
and the ppc_opts struct into GDB code ... Can't we ask a BFD routine
whether a particular CPU option is valid? E.g. by just making a "test"
call to print_insn_* and see if it succeeds?
Apart from those implementation details, I'm wondering whether we might
want to generalize the feature to allow setting any disassembler option,
not just CPU levels. Also, this could really be useful on any platform,
not just Power :-) But I see that some other architectures already use
info->disassembler_options to pass some special options, which might
make the generic solution more complex. Therefore I'd be OK with just
doing the Power implementation for now.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2016-09-30 16:19 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 [this message]
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
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=20160930161908.6A43511C24D@oc8523832656.ibm.com \
--to=uweigand@de.ibm.com \
--cc=amodra@gmail.com \
--cc=bergner@vnet.ibm.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
/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