From: Luis Machado <luis.machado@linaro.org>
To: Zied Guermazi <zied.guermazi@trande.de>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: A lean way for getting the size of the instruction at a given address
Date: Mon, 5 Apr 2021 10:01:55 -0300 [thread overview]
Message-ID: <476fcf13-8782-a69f-f43b-069497ba7e3b@linaro.org> (raw)
In-Reply-To: <442482d9-31bd-8101-38f0-fb7c7763e61c@trande.de>
Hi Zied,
On 4/4/21 4:59 AM, Zied Guermazi wrote:
> hi
>
> I need to get the size of the instruction at a given address. I am
> currently using gdb_insn_length (struct gdbarch *gdbarch, CORE_ADDR
> addr) which calls gdb_print_insn (struct gdbarch *gdbarch, CORE_ADDR
> memaddr, struct ui_file *stream, int *branch_delay_insns). and this is
> consuming a huge time, considering that this is used in branch tracing
> and this gets repeated up to few millions times.
>
>
> Is there a lean way for getting the size of the instruction at a given
> address, I am using it for aarch64 and arm targets.
At the moment I don't think there is an optimal solution for this. The
instruction length is calculated as part of the disassemble process, and
is tied to the function that prints instructions.
One way to speed things up is to have a new member function in "class
gdb_disassembler" to calculate the instruction length only.
Another way is to have a new gdbarch hook that calculates the size of an
instruction based on the current PC, mapping symbols etc.
>
> Kind Regards
>
> Zied Guermazi
>
>
next prev parent reply other threads:[~2021-04-05 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <295a186e-0dd9-fb96-671a-3df0a5611dd9@trande.de>
2021-04-04 7:59 ` Zied Guermazi
2021-04-05 13:01 ` Luis Machado [this message]
2021-04-05 16:17 ` Zied Guermazi
2021-04-05 16:40 ` Luis Machado
2021-04-05 21:47 ` Zied Guermazi
2021-04-05 22:04 ` Luis Machado
2021-04-05 22:12 ` Zied Guermazi
2021-04-05 22:15 ` Luis Machado
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=476fcf13-8782-a69f-f43b-069497ba7e3b@linaro.org \
--to=luis.machado@linaro.org \
--cc=gdb@sourceware.org \
--cc=zied.guermazi@trande.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).