public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Luis Machado <luisgpm@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb: aarch64: Remove MTE address checking from get_memtag
Date: Fri, 19 Apr 2024 14:31:02 +0000 (GMT)	[thread overview]
Message-ID: <20240419143102.7A523384AB7E@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=75606e5e8de136a1ad217e53ce5943a91d5ea424

commit 75606e5e8de136a1ad217e53ce5943a91d5ea424
Author: Gustavo Romero <gustavo.romero@linaro.org>
Date:   Thu Apr 18 20:10:32 2024 +0000

    gdb: aarch64: Remove MTE address checking from get_memtag
    
    This commit removes aarch64_linux_tagged_address_p from
    aarch64_linux_get_memtag. aarch64_linux_tagged_address_p checks if an
    address is tagged (MTE) or not.
    
    The check is redundant because aarch64_linux_get_memtag is always called
    from the upper layers (i.e. from printcmd.c via gdbarch hook
    gdbarch_get_memtag) after either gdbarch_tagged_address_p (that already
    points to aarch64_linux_tagged_address_p) has been called or
    after should_validate_memtags (that calls gdbarch_tagged_address_p at
    the end) has been called, so the address is already checked. Hence:
    
    a) in print_command_1, aarch64_linux_get_memtag (via gdbarch_get_memtag
    hook) is called but only after should_validate_memtags, which calls
    gdbarch_tagged_address_p;
    
    b) in do_examine, aarch64_linux_get_memtag is also called only after
    gdbarch_tagged_address_p is directly called;
    
    c) in memory_tag_check_command, gdbarch_get_memtag is called -- tags
    matching or not -- after the initial check via direct call to
    gdbarch_tagged_address_p;
    
    d) in memory_tag_print_tag_command, address is checked directly via
    gdbarch_tagged_address_p before gdbarch_get_memtag is called.
    
    Also, because after this change the address checking only happens at the
    upper layer it now allows the address checking to be specialized easily
    per target, via a target hook.
    
    Signed-off-by: Gustavo Romero <gustavo.romero@linaro.org>
    Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
    Approved-By: Luis Machado <luis.machado@arm.com>
    Tested-By: Luis Machado <luis.machado@arm.com>

Diff:
---
 gdb/aarch64-linux-tdep.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/gdb/aarch64-linux-tdep.c b/gdb/aarch64-linux-tdep.c
index 0b9784f38e4..50055ac3f48 100644
--- a/gdb/aarch64-linux-tdep.c
+++ b/gdb/aarch64-linux-tdep.c
@@ -2575,10 +2575,6 @@ aarch64_linux_get_memtag (struct gdbarch *gdbarch, struct value *address,
     tag = aarch64_mte_get_ltag (addr);
   else
     {
-      /* Make sure we are dealing with a tagged address to begin with.  */
-      if (!aarch64_linux_tagged_address_p (gdbarch, address))
-	return nullptr;
-
       /* Remove the top byte.  */
       addr = gdbarch_remove_non_address_bits (gdbarch, addr);
       std::optional<CORE_ADDR> atag = aarch64_mte_get_atag (addr);

                 reply	other threads:[~2024-04-19 14:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240419143102.7A523384AB7E@sourceware.org \
    --to=luisgpm@sourceware.org \
    --cc=gdb-cvs@sourceware.org \
    /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).