Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@vnet.ibm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: nickc@redhat.com, gdb-patches@sourceware.org,
	uweigand@de.ibm.com,        palves@redhat.com, amodra@gmail.com,
	binutils@sourceware.org
Subject: Re: [PATCH 1/2] Add support for setting disassembler-options in GDB for POWER, ARM and S390
Date: Fri, 18 Nov 2016 16:56:00 -0000	[thread overview]
Message-ID: <019eaf5d-9ace-539e-8501-feb3cb0eed6c@vnet.ibm.com> (raw)
In-Reply-To: <83eg28dcjk.fsf@gnu.org>

On 11/18/16 9:37 AM, Eli Zaretskii wrote:
>> Cc: gdb-patches@sourceware.org, Ulrich Weigand <uweigand@de.ibm.com>,        Pedro Alves <palves@redhat.com>, Alan Modra <amodra@gmail.com>,        binutils <binutils@sourceware.org>
>> From: Peter Bergner <bergner@vnet.ibm.com>
>> Date: Fri, 18 Nov 2016 09:10:38 -0600
>>
>> +* New commands
>> +
>> +set disassembler-options
>> +show disassembler-options
>> +  Controls the passing of target specific information to the disassembler.
>> +  Only supported on some targets.  If it is necessary to specify more than
>> +  one disassembler option then multiple options can be placed together into
>> +  a comma separated list.  Default is ''.
> 
> Thanks, but I think we should tell what systems support this.

Sure, how about the following?

Peter


diff --git a/gdb/NEWS b/gdb/NEWS
index a597405..54a6b7b 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -36,6 +36,16 @@
 
 Synopsys ARC                   arc*-*-elf32
 
+* New commands
+
+set disassembler-options
+show disassembler-options
+  Controls the passing of target specific information to the disassembler.
+  If it is necessary to specify more than one disassembler option then
+  multiple options can be placed together into a comma separated list.
+  Default is ''.  Currently the only supported targets are ARM, PowerPC
+  and S/390.
+
 *** Changes in GDB 7.12
 
 * GDB and GDBserver now build with a C++ compiler by default.


  reply	other threads:[~2016-11-18 16:56 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
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 [this message]
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=019eaf5d-9ace-539e-8501-feb3cb0eed6c@vnet.ibm.com \
    --to=bergner@vnet.ibm.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@redhat.com \
    --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