Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: allow default_addressable_memory_unit_size to handle more cases
Date: Wed, 21 Apr 2021 13:18:32 -0400	[thread overview]
Message-ID: <df054442-12fa-d7ab-6a6a-19d885b42ac3@polymtl.ca> (raw)
In-Reply-To: <20210421165919.1418455-1-andrew.burgess@embecosm.com>

On 2021-04-21 12:59 p.m., Andrew Burgess wrote:
> Currently default_addressable_memory_unit_size always returns 1,
> indicating 1 byte is 1 octet.  If a target has something other than
> this (common) setup then the target should override the
> default_addressable_memory_unit_size.
> 
> However, the bfd library already knows about each targets octets per
> byte, so it seems redundant making targets override this method to
> tell GDB something it already knows (through bfd).
> 
> In this commit I propose to make default_addressable_memory_unit_size
> return a value based on bfd's bits per byte.  I checked, and for every
> target that GDB currently supports the bits per byte in bfd is 8, so
> the current behaviour will not change.
> 
> In fact, the only targets in bfd that have bits per byte set to
> something other than 8 can be found in cpu-tic4x.c and cpu-tic54x.c, I
> don't believe these are supported by GDB right now.
> 
> I don't propose to remove the ability to override
> default_addressable_memory_unit_size, this allows targets additional
> flexibility for how to handle weird combinations of byte sizes.
> 
> This change was motivated by an out of tree target I was working on,
> but it seemed like it was a good change that others might benefit
> from.
> 
> There should be no user visible changes after this commit.
> 
> gdb/ChangeLog:
> 
> 	* arch-utils.c (default_addressable_memory_unit_size): Return a
> 	value based on bfd's bits per byte.
> ---
>  gdb/ChangeLog    | 5 +++++
>  gdb/arch-utils.c | 8 +++++---
>  2 files changed, 10 insertions(+), 3 deletions(-)
> 
> diff --git a/gdb/arch-utils.c b/gdb/arch-utils.c
> index e1d5afd6039..36681e96b61 100644
> --- a/gdb/arch-utils.c
> +++ b/gdb/arch-utils.c
> @@ -1005,13 +1005,15 @@ default_gnu_triplet_regexp (struct gdbarch *gdbarch)
>    return gdbarch_bfd_arch_info (gdbarch)->arch_name;
>  }
>  
> -/* Default method for gdbarch_addressable_memory_unit_size.  By default, a memory byte has
> -   a size of 1 octet.  */
> +/* Default method for gdbarch_addressable_memory_unit_size.  The default is
> +   based on the bits_per_byte defined in the bfd library for the current
> +   architecture, this is usually 8-bits, and so this function will usually
> +   return 1 indicating 1 bytes is 1 octet.  */
>  
>  int
>  default_addressable_memory_unit_size (struct gdbarch *gdbarch)
>  {
> -  return 1;
> +  return gdbarch_bfd_arch_info (gdbarch)->bits_per_byte / 8;
>  }
>  
>  void
> 

I think that makes sense, and therefore LGTM.

Simon

      reply	other threads:[~2021-04-21 17:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 16:59 Andrew Burgess
2021-04-21 17:18 ` Simon Marchi via Gdb-patches [this message]

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=df054442-12fa-d7ab-6a6a-19d885b42ac3@polymtl.ca \
    --to=gdb-patches@sourceware.org \
    --cc=andrew.burgess@embecosm.com \
    --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