From: Peter Bergner <bergner@vnet.ibm.com>
To: Pedro Alves <palves@redhat.com>, Ulrich Weigand <uweigand@de.ibm.com>
Cc: Alan Modra <amodra@gmail.com>,
gdb-patches@sourceware.org,
binutils <binutils@sourceware.org>
Subject: Re: [PATCH, RFC] Add support for choosing disassembler cpu in GDB for POWER.
Date: Fri, 28 Oct 2016 13:47:00 -0000 [thread overview]
Message-ID: <c4178472-1654-5700-0ba7-2d54eff74cf0@vnet.ibm.com> (raw)
In-Reply-To: <88940498-822b-b192-b983-d8571a81ad87@redhat.com>
On 10/27/16 4:40 AM, Pedro Alves wrote:
> I couldn't quite get why you need so much power specific parsing
> code in ppc-tdep.c, though. What would be necessary to be able to
> move most of that set/show handling to the common code?
Working on that now.
> I also wonder if you really want to stick with
> "set powerpc disassembler <cpu>" instead of
> "set powerpc disassembler-options <options>".
>
> I.e., I wonder about making the power one defined exactly like:
>
> "like 'set disassembler-options', but sets power disassembler
> options even if the current arch is not power."
Once we move all of this code to generic code, do we really
even need the arch specific command?
> The idea was to define the new command as exposing objdump's -M option:
>
> -M, --disassembler-options=OPT Pass text OPT on to the disassembler
>
> It happens that on power that allows only changing the cpu. Whereas
> for ARM that tweaks other things. x86 has options for both cpu and
> syntax. See what an --enable-targets=all build of
> objdump says in its --help:
Ok, got it.
Peter
next prev parent reply other threads:[~2016-10-28 13:47 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
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 [this message]
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=c4178472-1654-5700-0ba7-2d54eff74cf0@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