From: Alan Modra <amodra@gmail.com>
To: Peter Bergner <bergner@vnet.ibm.com>
Cc: Ulrich Weigand <uweigand@de.ibm.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, 06 Oct 2016 04:44:00 -0000 [thread overview]
Message-ID: <20161006044405.GY4877@bubble.grove.modra.org> (raw)
In-Reply-To: <5a66aca9-dfe9-7c44-21f9-27774a07d143@vnet.ibm.com>
On Wed, Oct 05, 2016 at 10:00:45PM -0500, Peter Bergner wrote:
> On 10/3/16 5:25 PM, Alan Modra wrote:
> > Somewhere in gdb you must be calling disassemble_init_for_target.
> > Why can't you call that again after setting the cpu (in struct
> > disassemble_info disassembler_options)?
>
> We (rs6000-tdep.c) don't call disassemble_init_for_target(). That is done
> by architecture independent gdb code before gdb_print_insn_powerpc() is
> ever called. We could call it from there, but as I mentioned in one of
> my previous notes, we'd be doing that before every insn we emit, which
> would be very expensive.
>
> The problem is, currently there is no way for the target to catch the
> disassembly initialization process to modify the struct disassemble_info
> disassembler_options value before we start emitting insns. That said,
> how about the following patch which adds that ability?
Thanks, the opcodes side of this patch looks OK to me.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2016-10-06 4:44 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 [this message]
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=20161006044405.GY4877@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=bergner@vnet.ibm.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--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