From: Simon Marchi <simark@simark.ca>
To: Luis <luis.machado.foss@gmail.com>
Cc: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
gdb-patches@sourceware.org,
Chris Packham <judge.packham@gmail.com>,
Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH v3 1/4] GDB: Add gdb/arch/aarch64-pauth-linux.h
Date: Sun, 22 Feb 2026 10:25:42 -0500 [thread overview]
Message-ID: <9c9a0b37-5cad-4dec-97fb-e84e2478858e@simark.ca> (raw)
In-Reply-To: <CANnS9rs5KKS0RzdgTdO_G_iVGw=G8C9-qitrrtmFVjv3g+dXEQ@mail.gmail.com>
On 2026-02-22 10:15, Luis wrote:
> That's ok by me. Would you like to clarify what Thiago needs to do so we don't send mixed signals then?
I think we can summarize it like this:
- Definitions in arch/ should be namespaced / prefixed with AARCH64_
(e.g. AARCH64_HWCAP_FOO)
- Definitions in nat/, which are there to allow building natively
against an older, should use the original name (e.g HWCAP_FOO)
- -tdep files should use the AARCH64_-prefixed versions (e.g.
AARCH64_HWCAP_FOO)
- -nat (in gdb) and -low (in gdbserver) should use the original name
(e.g. HWCAP_FOO)
Simon
next prev parent reply other threads:[~2026-02-22 15:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 6:00 [PATCH v3 0/4] GDB: aarch64-linux: Some header fixes Thiago Jung Bauermann
2026-02-17 6:00 ` [PATCH v3 1/4] GDB: Add gdb/arch/aarch64-pauth-linux.h Thiago Jung Bauermann
2026-02-21 12:14 ` Luis
2026-02-21 15:57 ` Simon Marchi
2026-02-22 10:06 ` Luis
2026-02-22 14:22 ` Simon Marchi
2026-02-22 15:15 ` Luis
2026-02-22 15:25 ` Simon Marchi [this message]
2026-03-03 5:00 ` Thiago Jung Bauermann
2026-02-17 6:01 ` [PATCH v3 2/4] GDB: Add gdb/arch/aarch64-fpmr-linux.h Thiago Jung Bauermann
2026-02-21 12:15 ` Luis
2026-02-17 6:01 ` [PATCH v3 3/4] GDB: aarch64-linux: Move definition of struct user_gcs Thiago Jung Bauermann
2026-02-21 12:20 ` Luis
2026-02-17 6:01 ` [PATCH v3 4/4] GDB: aarch64-linux: Fix build failure on musl systems Thiago Jung Bauermann
2026-02-21 12:23 ` Luis
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=9c9a0b37-5cad-4dec-97fb-e84e2478858e@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=judge.packham@gmail.com \
--cc=luis.machado.foss@gmail.com \
--cc=thiago.bauermann@linaro.org \
--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