Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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>
Subject: [PATCH v3 0/4] GDB: aarch64-linux: Some header fixes
Date: Tue, 17 Feb 2026 03:00:58 -0300	[thread overview]
Message-ID: <20260217060106.1906312-1-thiago.bauermann@linaro.org> (raw)

Patch 4 fixes the problem I set out to fix in v1¹ and v2².

Patches 1 and 2 are new in v3 and add new feature-specific AArch64 headers
in gdb/arch as suggested by Luis in his review o v2.

Patch 3 is v2's patch 1 and grew out of Simon's patch review of v1, where
he noted that files in gdb/arch/ shouldn't depend on arch-specific include
files.

Thiago Jung Bauermann (4):
  GDB: Add gdb/arch/aarch64-pauth-linux.h
  GDB: Add gdb/arch/aarch64-fpmr-linux.h
  GDB: aarch64-linux: Move definition of struct user_gcs
  GDB: aarch64-linux: Fix build failure on musl systems

 gdb/Makefile.in                    |  3 +++
 gdb/aarch64-linux-nat.c            |  5 +++-
 gdb/aarch64-linux-tdep.c           |  9 ++++---
 gdb/aarch64-linux-tdep.h           |  6 -----
 gdb/arch/aarch64-fpmr-linux.h      | 28 +++++++++++++++++++++
 gdb/arch/aarch64-gcs-linux.h       | 17 ++-----------
 gdb/arch/aarch64-pauth-linux.h     | 31 ++++++++++++++++++++++++
 gdb/arch/aarch64.h                 |  8 ------
 gdb/nat/aarch64-gcs-linux-ptrace.h | 39 ++++++++++++++++++++++++++++++
 gdbserver/linux-aarch64-low.cc     | 10 ++++----
 gdbsupport/config.in               |  3 +++
 gdbsupport/configure               | 36 +++++++++++++++++++++++++++
 gdbsupport/configure.ac            | 19 +++++++++++++++
 13 files changed, 176 insertions(+), 38 deletions(-)
 create mode 100644 gdb/arch/aarch64-fpmr-linux.h
 create mode 100644 gdb/arch/aarch64-pauth-linux.h
 create mode 100644 gdb/nat/aarch64-gcs-linux-ptrace.h

¹ https://inbox.sourceware.org/gdb-patches/20260211045853.1436881-1-thiago.bauermann@linaro.org/
² https://inbox.sourceware.org/gdb-patches/20260214045504.361392-1-thiago.bauermann@linaro.org/

             reply	other threads:[~2026-02-17  6:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17  6:00 Thiago Jung Bauermann [this message]
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
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=20260217060106.1906312-1-thiago.bauermann@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=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