Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Simon Marchi <simark@simark.ca>
Cc: Luis <luis.machado.foss@gmail.com>,
	 gdb-patches@sourceware.org,
	 Chris Packham <judge.packham@gmail.com>,
	 Tom Tromey <tom@tromey.com>,
	sunilkumar.dora@windriver.com
Subject: Re: [PATCH v4 0/6] GDB: aarch64-linux: Some header fixes
Date: Tue, 17 Mar 2026 20:43:16 -0300	[thread overview]
Message-ID: <87tsuec99n.fsf@linaro.org> (raw)
In-Reply-To: <59958a12-9ef7-4b37-9f34-2769ab061d8e@simark.ca> (Simon Marchi's message of "Mon, 16 Mar 2026 22:49:01 -0400")

Simon Marchi <simark@simark.ca> writes:

> On 2026-03-16 22:29, Thiago Jung Bauermann wrote:
>> Hello,
>> 
>> Luis <luis.machado.foss@gmail.com> writes:
>> 
>>> Thanks. I think v4 is good.
>> 
>> Thank you! I waited a bit to see if Simon wanted to chime in again on
>> the discussion about using struct user_pac_mask in patch 1. I'll create
>> an RFC patch implementing that idea and post it separately.
>
> It's just an idea, do it if you think it makes sense and it's not too
> complicated.  I thought it could help show that the magic size doesn't
> come from nowhere.  But there is not advantage beyond that.

Thank you. I experimented with it but im my view it's not worth the
extra configure boilerplate.

Unlike the GCS code which actually uses the struct user_gcs definition,
the PAuth register fetching/writing code uses a two-element array of
uint64_t and would benefit little from a rewrite to use members of
struct user_pac_mask instead.
-- 
Thiago

      reply	other threads:[~2026-03-17 23:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-03  5:06 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
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 [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=87tsuec99n.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