Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@vnet.ibm.com>
To: gdb-patches@sourceware.org
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
	Pedro Alves <palves@redhat.com>,
	       Alan Modra <amodra@gmail.com>,
	binutils <binutils@sourceware.org>
Subject: Re: [PATCH 1/2] Add support for setting disassembler-options in GDB for POWER, ARM and S390
Date: Thu, 17 Nov 2016 19:52:00 -0000	[thread overview]
Message-ID: <b879bc9d-e6cf-b9d8-bfcc-7e46c3864f51@vnet.ibm.com> (raw)
In-Reply-To: <b6037acd-9036-7e69-3350-8da5f0ec981b@vnet.ibm.com>

On 11/17/16 1:18 PM, Peter Bergner wrote:
> Ping.  This is the same as my last patch posted here:
>
>     https://sourceware.org/ml/binutils/2016-11/msg00029.html
>
> ...except for that we no longer output "default" for a NULL
> disassembler_options value, and instead just output ''.
> I will note that doing "set disassembler-options" does reset
> the disassembler_options value to NULL.

I will note I only tested ARM and S390 using a cross debugger,
but they seem to work fine.  In addition, I was able to confirm
that using "set disassembler-options ..." and "set arm disassembler ..."
together works fine, meaning you can use them interchangeably.
The only "gotcha", is that "set arm disassembler ..." uses short
option names, while the "set disassebler-options ..." has to use
the canonical long names (eg, "set arm disassembler atpcs" versus
"set disassembler-options reg-names-atpcs").

That above said, a little testing of ARM and S390 by others would
be appreciated.

I did try and take a stab converting i386 over as well, but
opcodes/i386-dis.c:print_insn() contains a lot of global
state that really should be moved into a disassemble_init_i386()
similar to what I did for S390.  There really is no reason to
parse info->disassembler_options for each insn we print.
However, I didn't trust myself at getting that all correct, so
I'll leave it to someone more qualified to do.

Peter



  reply	other threads:[~2016-11-17 19:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 19:19 Peter Bergner
2016-11-17 19:52 ` Peter Bergner [this message]
2016-11-18 10:25 ` Nick Clifton
2016-11-18 15:10   ` Peter Bergner
2016-11-18 15:38     ` Eli Zaretskii
2016-11-18 16:56       ` Peter Bergner
2016-11-18 17:08         ` Eli Zaretskii
2016-11-18 17:23         ` Pedro Alves
2016-11-22 17:04           ` Peter Bergner
2016-11-22 17:40             ` Pedro Alves
2017-01-23 23:35           ` Peter Bergner
2017-01-24  1:57             ` Alan Modra
2017-01-24  2:39               ` Peter Bergner
2017-01-24  3:36                 ` Alan Modra
2017-01-24  4:32                   ` Peter Bergner
2017-01-24 16:00                     ` Peter Bergner
2017-01-25  4:31                       ` Alan Modra
2017-01-25 17:20                         ` Peter Bergner
2017-01-24  3:29             ` Eli Zaretskii
     [not found]             ` <20170125142335.GT28060@E107787-LIN>
2017-01-25 14:30               ` Peter Bergner
2017-01-31 21:13               ` Peter Bergner
2017-02-01 21:44                 ` Yao Qi

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=b879bc9d-e6cf-b9d8-bfcc-7e46c3864f51@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