From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: gdb-patches@sourceware.org
Cc: Chris Packham <judge.packham@gmail.com>,
Luis <luis.machado.foss@gmail.com>, Tom Tromey <tom@tromey.com>,
Simon Marchi <simark@simark.ca>,
sunilkumar.dora@windriver.com
Subject: Re: [PATCH v4 3/6] GDB: aarch64-linux: Reorganize MTE-related definitions
Date: Wed, 04 Mar 2026 01:17:53 -0300 [thread overview]
Message-ID: <874imwcjny.fsf@linaro.org> (raw)
In-Reply-To: <20260303050641.198127-4-thiago.bauermann@linaro.org> (Thiago Jung Bauermann's message of "Tue, 3 Mar 2026 02:06:38 -0300")
Thiago Jung Bauermann <thiago.bauermann@linaro.org> writes:
> diff --git a/gdb/nat/aarch64-mte-linux-ptrace.h b/gdb/nat/aarch64-mte-linux-ptrace.h
> index d31fa9f3c071..653de33108c8 100644
> --- a/gdb/nat/aarch64-mte-linux-ptrace.h
> +++ b/gdb/nat/aarch64-mte-linux-ptrace.h
> @@ -20,6 +20,11 @@
> #ifndef GDB_NAT_AARCH64_MTE_LINUX_PTRACE_H
> #define GDB_NAT_AARCH64_MTE_LINUX_PTRACE_H
>
> +/* Feature check for Memory Tagging Extension. */
> +#ifndef HWCAP2_MTE
> +#define HWCAP2_MTE (1 << 18)
> +#endif
> +
> /* MTE allocation tag access */
>
> #ifndef PTRACE_PEEKMTETAGS
As with the previous patches, I locally amended this one to also include
<asm/hwcap.h>. And since this header also defines some ptrace constants,
also include <asm/ptrace.h>:
diff --git a/gdb/nat/aarch64-mte-linux-ptrace.h b/gdb/nat/aarch64-mte-linux-ptrace.h
index 653de33108c8..7d1e7c1960d1 100644
--- a/gdb/nat/aarch64-mte-linux-ptrace.h
+++ b/gdb/nat/aarch64-mte-linux-ptrace.h
@@ -20,6 +20,9 @@
#ifndef GDB_NAT_AARCH64_MTE_LINUX_PTRACE_H
#define GDB_NAT_AARCH64_MTE_LINUX_PTRACE_H
+#include <asm/hwcap.h>
+#include <asm/ptrace.h>
+
/* Feature check for Memory Tagging Extension. */
#ifndef HWCAP2_MTE
#define HWCAP2_MTE (1 << 18)
--
Thiago
next prev parent reply other threads:[~2026-03-04 4:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 5:06 [PATCH v4 0/6] GDB: aarch64-linux: Some header fixes Thiago Jung Bauermann
2026-03-03 5:06 ` [PATCH v4 1/6] GDB: Add aarch64-pauth-linux.h to gdb/arch/ and gdb/nat/ Thiago Jung Bauermann
2026-03-03 15:51 ` Simon Marchi
2026-03-04 4:04 ` Thiago Jung Bauermann
2026-03-10 14:18 ` Luis
2026-03-04 3:59 ` Thiago Jung Bauermann
2026-03-03 5:06 ` [PATCH v4 2/6] GDB: Add aarch64-fpmr-linux.h " Thiago Jung Bauermann
2026-03-04 4:14 ` Thiago Jung Bauermann
2026-03-10 14:14 ` Luis
2026-03-03 5:06 ` [PATCH v4 3/6] GDB: aarch64-linux: Reorganize MTE-related definitions Thiago Jung Bauermann
2026-03-04 4:17 ` Thiago Jung Bauermann [this message]
2026-03-10 14:12 ` Luis
2026-03-03 5:06 ` [PATCH v4 4/6] GDB: aarch64-linux: Reorganize SME-related definitions Thiago Jung Bauermann
2026-03-04 4:21 ` Thiago Jung Bauermann
2026-03-10 14:07 ` Luis
2026-03-03 5:06 ` [PATCH v4 5/6] GDB: aarch64-linux: Reorganize GCS-related definitions Thiago Jung Bauermann
2026-03-04 4:27 ` Thiago Jung Bauermann
2026-03-10 14:05 ` Luis
2026-03-03 5:06 ` [PATCH v4 6/6] GDB: aarch64-linux: Fix build failure on musl systems Thiago Jung Bauermann
2026-03-03 16:14 ` [PATCH v4 0/6] GDB: aarch64-linux: Some header fixes Simon Marchi
2026-03-04 3:52 ` Thiago Jung Bauermann
2026-03-10 14:19 ` Luis
2026-03-17 2:29 ` Thiago Jung Bauermann
2026-03-17 2:49 ` Simon Marchi
2026-03-17 23:43 ` Thiago Jung Bauermann
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=874imwcjny.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=judge.packham@gmail.com \
--cc=luis.machado.foss@gmail.com \
--cc=simark@simark.ca \
--cc=sunilkumar.dora@windriver.com \
--cc=tom@tromey.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