Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: John Baldwin <jhb@FreeBSD.org>,
	binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH 04/12] Add an arm-tls feature which includes the tpidruro register from CP15.
Date: Mon, 4 Apr 2022 09:01:50 +0100	[thread overview]
Message-ID: <31fefe5b-4fe5-3e3b-5eeb-b1328c584916@arm.com> (raw)
In-Reply-To: <20220323210048.25525-5-jhb@FreeBSD.org>

Hi,

On 3/23/22 21:00, John Baldwin wrote:
> ---
>   gdb/arch/aarch32.c           |  2 ++
>   gdb/arch/arm.c               |  6 +++++-
>   gdb/arch/arm.h               |  7 ++++---
>   gdb/arm-fbsd-tdep.c          |  4 ++--
>   gdb/arm-linux-nat.c          |  6 +++---
>   gdb/arm-linux-tdep.c         |  4 ++--
>   gdb/arm-netbsd-nat.c         |  4 ++--
>   gdb/arm-tdep.c               | 20 +++++++++++++++-----
>   gdb/arm-tdep.h               |  2 +-
>   gdb/features/Makefile        |  1 +
>   gdb/features/arm/arm-tls.c   | 14 ++++++++++++++
>   gdb/features/arm/arm-tls.xml | 11 +++++++++++
>   12 files changed, 62 insertions(+), 19 deletions(-)
>   create mode 100644 gdb/features/arm/arm-tls.c
>   create mode 100644 gdb/features/arm/arm-tls.xml
> 
> diff --git a/gdb/arch/aarch32.c b/gdb/arch/aarch32.c
> index 0c544d381f1..4d6ffb44a15 100644
> --- a/gdb/arch/aarch32.c
> +++ b/gdb/arch/aarch32.c
> @@ -19,6 +19,7 @@
>   #include "aarch32.h"
>   
>   #include "../features/arm/arm-core.c"
> +#include "../features/arm/arm-tls.c"
>   #include "../features/arm/arm-vfpv3.c"
>   
>   /* See aarch32.h.  */
> @@ -38,6 +39,7 @@ aarch32_create_target_description ()
>     /* Create a vfpv3 feature, then a blank NEON feature.  */
>     regnum = create_feature_arm_arm_vfpv3 (tdesc.get (), regnum);
>     tdesc_create_feature (tdesc.get (), "org.gnu.gdb.arm.neon");
> +  regnum = create_feature_arm_arm_tls (tdesc.get (), regnum);
>   
>     return tdesc.release ();
>   }
> diff --git a/gdb/arch/arm.c b/gdb/arch/arm.c
> index 126e46a950a..15b600e22f4 100644
> --- a/gdb/arch/arm.c
> +++ b/gdb/arch/arm.c
> @@ -22,6 +22,7 @@
>   #include "arm.h"
>   
>   #include "../features/arm/arm-core.c"
> +#include "../features/arm/arm-tls.c"
>   #include "../features/arm/arm-vfpv2.c"
>   #include "../features/arm/arm-vfpv3.c"
>   #include "../features/arm/xscale-iwmmxt.c"
> @@ -373,7 +374,7 @@ shifted_reg_val (struct regcache *regcache, unsigned long inst,
>   /* See arch/arm.h.  */
>   
>   target_desc *
> -arm_create_target_description (arm_fp_type fp_type)
> +arm_create_target_description (arm_fp_type fp_type, bool tls)
>   {
>     target_desc_up tdesc = allocate_target_description ();
>   
> @@ -409,6 +410,9 @@ arm_create_target_description (arm_fp_type fp_type)
>         error (_("Invalid Arm FP type: %d"), fp_type);
>       }
>   
> +  if (tls)
> +    regnum = create_feature_arm_arm_tls (tdesc.get (), regnum);
> +
>     return tdesc.release ();
>   }
>   
> diff --git a/gdb/arch/arm.h b/gdb/arch/arm.h
> index f75470e7572..32f29b20d33 100644
> --- a/gdb/arch/arm.h
> +++ b/gdb/arch/arm.h
> @@ -49,6 +49,7 @@ enum gdb_regnum {
>     ARM_D0_REGNUM,		/* VFP double-precision registers.  */
>     ARM_D31_REGNUM = ARM_D0_REGNUM + 31,
>     ARM_FPSCR_REGNUM,
> +  ARM_TPIDRURO_REGNUM,
>   
>     /* Other useful registers.  */
>     ARM_FP_REGNUM = 11,		/* Frame register in ARM code, if used.  */
> @@ -65,8 +66,8 @@ enum arm_register_counts {
>     ARM_NUM_ARG_REGS = 4,
>     /* Number of floating point argument registers.  */
>     ARM_NUM_FP_ARG_REGS = 4,
> -  /* Number of registers (old, defined as ARM_FPSCR_REGNUM + 1.  */
> -  ARM_NUM_REGS = ARM_FPSCR_REGNUM + 1
> +  /* Number of registers (old, defined as ARM_TPIDRURO_REGNUM + 1.  */
> +  ARM_NUM_REGS = ARM_TPIDRURO_REGNUM + 1
>   };

I'm attempting to move away from these hardcoded register numbers. If 
there are optional features, that means ARM_NUM_REGS won't reflect the 
reality anymore, and there may be holes in the register numbering.

For example, a bare metal target may not have ARM_TPIDRURO_REGNUM. The 
correct way is to account for it dynamically, similar to what we do with 
MVE (and to what we do for pauth, MTE and your TLS handling).

  reply	other threads:[~2022-04-04  8:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 21:00 [PATCH 00/12] * Support for Thread Local Storage (TLS) variables on FreeBSD arm and aarch64 architectures John Baldwin
2022-03-23 21:00 ` [PATCH 01/12] Handle another edge case for TLS variable lookups John Baldwin
2022-03-23 23:55   ` John Baldwin
2022-03-24  0:26     ` John Baldwin
2022-03-23 21:00 ` [PATCH 02/12] fbsd-nat: Add helper routines for register sets using PT_[G]SETREGSET John Baldwin
2022-03-24  8:51   ` Luis Machado via Gdb-patches
2022-03-24 17:45     ` John Baldwin
2022-03-23 21:00 ` [PATCH 03/12] Create pseudo sections for NT_ARM_TLS notes on FreeBSD John Baldwin
2022-03-23 21:00 ` [PATCH 04/12] Add an arm-tls feature which includes the tpidruro register from CP15 John Baldwin
2022-04-04  8:01   ` Luis Machado via Gdb-patches [this message]
2022-04-12 23:36     ` John Baldwin
2022-04-14 10:23       ` Luis Machado via Gdb-patches
2022-04-19 16:18         ` John Baldwin
2022-04-20  6:59           ` Luis Machado via Gdb-patches
2022-03-23 21:00 ` [PATCH 05/12] Read the tpidruro register from NT_ARM_TLS core dump notes on FreeBSD/arm John Baldwin
2022-03-23 21:00 ` [PATCH 06/12] Support TLS variables " John Baldwin
2022-03-23 21:00 ` [PATCH 07/12] Fetch the NT_ARM_TLS register set for native FreeBSD/arm processes John Baldwin
2022-03-23 21:00 ` [PATCH 08/12] Add an aarch64-tls feature which includes the tpidr register John Baldwin
2022-03-28 10:16   ` Luis Machado via Gdb-patches
2022-04-01 23:30     ` John Baldwin
2022-04-04  8:06       ` Luis Machado via Gdb-patches
2022-04-04 12:18         ` Luis Machado via Gdb-patches
2022-05-03 21:14   ` Luis Machado via Gdb-patches
2022-05-03 21:30     ` John Baldwin
2022-05-03 21:34       ` Luis Machado via Gdb-patches
2022-03-23 21:00 ` [PATCH 09/12] Read the tpidr register from NT_ARM_TLS core dump notes on FreeBSD/Aarch64 John Baldwin

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=31fefe5b-4fe5-3e3b-5eeb-b1328c584916@arm.com \
    --to=gdb-patches@sourceware.org \
    --cc=binutils@sourceware.org \
    --cc=jhb@FreeBSD.org \
    --cc=luis.machado@arm.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