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: Thu, 03 Nov 2016 15:02:00 -0000 [thread overview]
Message-ID: <25f99efc-6ff0-3908-dbab-fe3792be770f@vnet.ibm.com> (raw)
In-Reply-To: <8733fac4-9e5d-43de-75a6-0f191c4000e7@redhat.com>
On 11/3/16 6:01 AM, Pedro Alves wrote:
> On 10/28/2016 03:53 PM, Peter Bergner wrote:
> BTW, I'm also not sure about saying "default" in "show disassembler-options".
> I don't think "set disassembler-options default" would work?
> Do we still need that given the option is no longer described in
> terms of cpus?
Uli and I discussed this here:
https://sourceware.org/ml/gdb-patches/2016-10/msg00184.html
https://sourceware.org/ml/gdb-patches/2016-10/msg00188.html
Uli didn't like (at least the way the code was written in the earlier
patch) how I was trying to initialize the disassembler_options
to a default. He thought that just leaving disassembler_options NULL
and letting the arch choose its default was best. That's when I added
the code to emit "default" whenever disassembler_options is NULL.
> Related, "set disassembler-options" should work to clear options.
> I couldn't tell whether it works from a quick skim over your
> latest patch.
As part of my last patch:
https://sourceware.org/ml/gdb-patches/2016-11/msg00023.html
...is said:
> Secondly, I wanted a way for the user to go back to the default
> (ie, NULL) disassembler option. I could only do that first I
> removed white space. I added the comma cleanup since it was
> easy.
So yes, we can go back to the NULL default.
Peter
next prev parent reply other threads:[~2016-11-03 15:02 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
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 [this message]
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=25f99efc-6ff0-3908-dbab-fe3792be770f@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