public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] gdb: remove target_ops parameter from gdbarch_core_read_description
Date: Tue, 29 Nov 2022 11:16:00 -0800	[thread overview]
Message-ID: <1c3f0845-634d-9d6a-4cc1-d75e136d099b@FreeBSD.org> (raw)
In-Reply-To: <20221129025048.44490-3-simon.marchi@polymtl.ca>

On 11/28/22 6:50 PM, Simon Marchi via Gdb-patches wrote:
> Following the previous patch ("gdb: change order of core_target
> initialization"), it is no longer necessary for the core target to pass
> a pointer to itself to gdbarch_core_read_description.  Implementations
> of this method can just do regular calls to target_read_auxv, through
> the inferior target stack.
> 
> This allows removing the target_ops parameter in
> gdbarch_core_read_description and a bunch of functions called
> downstream.  Some auxv-related functions received the auxv data as a
> parameter, since they could not assume it could be read from the current
> inferior, that is also no longer needed.
> 
> Regression tested.  I also tested manually against an AArch64 MTE test
> case that Luis Machado sent me a while ago when we were working on this
> auxv caching issue, the desired behavior of reporting the MTE tags when
> opening the code still worked.
> 
> Change-Id: I1e00361209028e9b65dde085d383cf950a7b5e3a
> ---
>   gdb/aarch64-fbsd-tdep.c   |  3 +--
>   gdb/aarch64-linux-tdep.c  |  8 +++-----
>   gdb/amd64-fbsd-tdep.c     |  4 +---
>   gdb/amd64-linux-tdep.c    |  4 +---
>   gdb/arc-linux-tdep.c      |  4 +---
>   gdb/arm-fbsd-tdep.c       | 24 +++++-------------------
>   gdb/arm-fbsd-tdep.h       | 15 +++++----------
>   gdb/arm-linux-tdep.c      |  7 ++-----
>   gdb/auxv.c                | 11 ++---------
>   gdb/auxv.h                |  4 ----
>   gdb/corelow.c             |  2 +-
>   gdb/gdbarch-components.py |  2 +-
>   gdb/gdbarch-gen.h         |  4 ++--
>   gdb/gdbarch.c             |  4 ++--
>   gdb/i386-fbsd-tdep.c      |  4 +---
>   gdb/i386-linux-tdep.c     |  4 +---
>   gdb/linux-tdep.c          | 24 ++++++++++--------------
>   gdb/linux-tdep.h          | 14 ++++++--------
>   gdb/mips-linux-tdep.c     |  4 +---
>   gdb/ppc-linux-tdep.c      |  7 ++-----
>   gdb/s390-linux-tdep.c     |  6 ++----
>   21 files changed, 50 insertions(+), 109 deletions(-)
> 
> diff --git a/gdb/arm-fbsd-tdep.c b/gdb/arm-fbsd-tdep.c
> index 75ee08eba506..4ea238de7c7f 100644
> --- a/gdb/arm-fbsd-tdep.c
> +++ b/gdb/arm-fbsd-tdep.c
> @@ -215,10 +215,11 @@ arm_fbsd_iterate_over_regset_sections (struct gdbarch *gdbarch,
>   /* See arm-fbsd-tdep.h.  */
>   
>   const struct target_desc *
> -arm_fbsd_read_description_auxv (const gdb::optional<gdb::byte_vector> &auxv,
> -				target_ops *target, gdbarch *gdbarch, bool tls)
> +arm_fbsd_read_description_auxv (gdbarch *gdbarch, bool tls)
>   {
>     CORE_ADDR arm_hwcap = 0;
> +  gdb::optional<gdb::byte_vector> auxv = target_read_auxv ();
> +  target_ops *target = current_inferior ()->top_target ();
>   
>     if (!auxv.has_value ()
>         || target_auxv_search (*auxv, target, gdbarch, AT_FREEBSD_HWCAP,
> @@ -239,29 +240,14 @@ arm_fbsd_read_description_auxv (const gdb::optional<gdb::byte_vector> &auxv,
>     return arm_read_description (ARM_FP_TYPE_NONE, tls);
>   }
>   
> -/* See arm-fbsd-tdep.h.  */
> -
> -const struct target_desc *
> -arm_fbsd_read_description_auxv (bool tls)
> -{
> -  gdb::optional<gdb::byte_vector> auxv = target_read_auxv ();
> -  return arm_fbsd_read_description_auxv (auxv,
> -					 current_inferior ()->top_target (),
> -					 current_inferior ()->gdbarch,
> -					 tls);
> -}
> -

This function is used by arm-fbsd-nat.c in the read_description target
method.  Probably that function just needs to be updated to pass in the
gdbarch explicitly rather than keeping this wrapper method though:

diff --git a/gdb/arm-fbsd-nat.c b/gdb/arm-fbsd-nat.c
index 340b8e0d710..0ed3104d12d 100644
--- a/gdb/arm-fbsd-nat.c
+++ b/gdb/arm-fbsd-nat.c
@@ -96,7 +96,7 @@ arm_fbsd_nat_target::read_description ()
  #ifdef PT_GETREGSET
    tls = have_regset (inferior_ptid, NT_ARM_TLS) != 0;
  #endif
-  desc = arm_fbsd_read_description_auxv (tls);
+  desc = arm_fbsd_read_description_auxv (current_inferior ()->gdbarch, tls);
    if (desc == NULL)
      desc = this->beneath ()->read_description ();
    return desc;

-- 
John Baldwin


  reply	other threads:[~2022-11-29 19:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29  2:50 [PATCH 1/3] gdb: add inferior_target_stack_changed observer, use it to clear auxv cache Simon Marchi
2022-11-29  2:50 ` [PATCH 2/3] gdb: break up core_target initialization Simon Marchi
2022-11-29 19:27   ` John Baldwin
2022-11-29 21:53     ` Simon Marchi
2022-11-30 17:29       ` John Baldwin
2022-11-30 16:05   ` Tom Tromey
2022-12-02 19:38     ` Simon Marchi
2022-11-29  2:50 ` [PATCH 3/3] gdb: remove target_ops parameter from gdbarch_core_read_description Simon Marchi
2022-11-29 19:16   ` John Baldwin [this message]
2022-11-29 21:45     ` Simon Marchi
2022-12-02 20:51   ` [PATCH v1.1 " Simon Marchi
2022-11-30 15:44 ` [PATCH 1/3] gdb: add inferior_target_stack_changed observer, use it to clear auxv cache Tom Tromey
2022-12-02 19:36   ` Simon Marchi
2022-12-02 20:59     ` Tom Tromey

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=1c3f0845-634d-9d6a-4cc1-d75e136d099b@FreeBSD.org \
    --to=jhb@freebsd.org \
    --cc=gdb-patches@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).