From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org,
Chris Packham <judge.packham@gmail.com>,
Luis <luis.machado.foss@gmail.com>, Tom Tromey <tom@tromey.com>,
sunilkumar.dora@windriver.com
Subject: Re: [PATCH v4 1/6] GDB: Add aarch64-pauth-linux.h to gdb/arch/ and gdb/nat/
Date: Wed, 04 Mar 2026 01:04:49 -0300 [thread overview]
Message-ID: <87ldg8ck9q.fsf@linaro.org> (raw)
In-Reply-To: <8e20892a-b4ed-47c1-90bc-69d8d948aafa@simark.ca> (Simon Marchi's message of "Tue, 3 Mar 2026 10:51:28 -0500")
Simon Marchi <simark@simark.ca> writes:
>> diff --git a/gdbserver/linux-aarch64-low.cc b/gdbserver/linux-aarch64-low.cc
>> index b19e605f55d6..07ddfb324466 100644
>> --- a/gdbserver/linux-aarch64-low.cc
>> +++ b/gdbserver/linux-aarch64-low.cc
>> @@ -22,6 +22,7 @@
>> #include "linux-low.h"
>> #include "nat/aarch64-linux.h"
>> #include "nat/aarch64-linux-hw-point.h"
>> +#include "nat/aarch64-pauth-linux.h"
>> #include "arch/aarch64-insn.h"
>> #include "linux-aarch32-low.h"
>> #include "elf/common.h"
>> @@ -41,6 +42,7 @@
>> #include "arch/aarch64.h"
>> #include "arch/aarch64-gcs-linux.h"
>> #include "arch/aarch64-mte-linux.h"
>> +#include "arch/aarch64-pauth-linux.h"
>> #include "arch/aarch64-scalable-linux.h"
>> #include "linux-aarch32-tdesc.h"
>> #include "linux-aarch64-tdesc.h"
>> @@ -952,7 +954,7 @@ aarch64_adjust_register_sets (const struct aarch64_features &features)
>> break;
>> case NT_ARM_PAC_MASK:
>> if (features.pauth)
>> - regset->size = AARCH64_PAUTH_REGS_SIZE;
>> + regset->size = AARCH64_LINUX_SIZEOF_PAUTH;
>
> It's not a deal-breaker for this patch series, but I'm just wondering:
> is there some "native" thing, provided by Linux, that could give us the
> size here, like sizeof(some_type)? If we're trying to use the native
> stuff in the native files, then for consistency it would be nice to
> avoid relying on our own definition of the sizeof pauth.
There's struct user_pac_mask in <asm/ptrace.h> so we could do
sizeof (user_pac_mask), but to allow using older system headers that would
require a configure test as done in patch 6 of this series, and add our
own definition of the struct in case the system headers don't have it.
I can do that as a separate patch if you think it's better.
--
Thiago
next prev parent reply other threads:[~2026-03-04 4:05 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 [this message]
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
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=87ldg8ck9q.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