From: Zied Guermazi <zied.guermazi@trande.de>
To: Simon Marchi <simon.marchi@polymtl.ca>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: flag to know that we are compiling GDB for an arm target
Date: Mon, 22 Mar 2021 03:46:00 +0100 [thread overview]
Message-ID: <4d77ba55-5ca6-4b44-2cc7-ecbb37ff26b6@trande.de> (raw)
In-Reply-To: <73d48246-983d-5b0b-be40-dee0423daf43@polymtl.ca>
hi Simon,
I am extending btrace for armv7 and armv8. In armv7, due to some
limitations in the debug HW, GDB requires the current program status
register CPSR to know in which ISA mode it is, so that it can set
breakpoints properly and calculate the "landing" address for next,
nexti, step commands
When we use the traces in replay mode we need to know and provide the
cpsr at any instruction.
there is a data structure (btrace_insn in btrace.h) that was extended to
holds cpsr register and possibly other registers (paving the way for
data tracing). currently it is a vector of registers, that will be
(currently) empty of all architectures except ARMv7 (see the struct
below). We have typically thousands to millions instances of this structure.
struct btrace_insn
{
/* The address of this instruction. */
CORE_ADDR pc;
/* The size of this instruction in bytes. */
gdb_byte size;
/* A vector of registers. */
std::vector<record_btrace_reg_entry> registers;
/* The instruction class of this instruction. */
enum btrace_insn_class iclass;
/* A bit vector of BTRACE_INSN_FLAGS. */
btrace_insn_flags flags;
};
the empty vector was judged to be a big overhead for Intel PT for
example. I am looking for a way to inhibit it, when we are not building
GDB for armv7.
do you have any proposal for solving such a situation?
On 22.03.21 03:26, Simon Marchi wrote:
>
> On 2021-03-21 10:21 p.m., Zied Guermazi wrote:
>> hi,
>>
>> is it possible to know, at compile time, whether we are compiling gdb for an armv7 target ( e.g arm-linux, arm-none-eabi ... ) or not? for example a define that gets propagated to source/header files.
>>
>> Kind Regards
>>
>> Zied Guermazi
>>
>>
> Not really, since one GDB can be configured for multiple target
> architectures (you can include all possible target architectures with
> --enable-targets=all when running configure).
>
> What are you trying to achieve?
>
> Simon
--
*Zied Guermazi*
founder
Trande UG
Leuschnerstraße 2
69469 Weinheim/Germany
Mobile: +491722645127
mailto:zied.guermazi@trande.de
*Trande UG*
Leuschnerstraße 2, D-69469 Weinheim; Telefon: +491722645127
Sitz der Gesellschaft: Weinheim- Registergericht: AG Mannheim HRB 736209
- Geschäftsführung: Zied Guermazi
*Confidentiality Note*
This message is intended only for the use of the named recipient(s) and
may contain confidential and/or privileged information. If you are not
the intended recipient, please contact the sender and delete the
message. Any unauthorized use of the information contained in this
message is prohibited.
next prev parent reply other threads:[~2021-03-22 2:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 2:21 Zied Guermazi
2021-03-22 2:26 ` Simon Marchi
2021-03-22 2:46 ` Zied Guermazi [this message]
2021-03-22 3:40 ` Simon Marchi
2021-03-22 3:59 ` Zied Guermazi
2021-03-22 8:29 ` Metzger, Markus T
2021-03-22 14:53 ` Zied Guermazi
2021-03-22 15:06 ` Simon Marchi
2021-03-22 15:13 ` Zied Guermazi
2021-03-22 15:22 ` Metzger, Markus T
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=4d77ba55-5ca6-4b44-2cc7-ecbb37ff26b6@trande.de \
--to=zied.guermazi@trande.de \
--cc=gdb@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).