From: Luis Machado <luis.machado.foss@gmail.com>
To: gdb-patches@sourceware.org, thiago.bauermann@linaro.org,
Alan.Hayward@arm.com
Subject: [PATCH] [ANNOUNCEMENT] [AArch64/Arm] Maintainership updates
Date: Fri, 27 Mar 2026 16:09:20 +0000 [thread overview]
Message-ID: <20260327160920.3809-1-luis.machado.foss@gmail.com> (raw)
Hi,
I am writing to announce a change in the maintainership for the AArch64 and Arm
architectures.
After several years of dedicated service, Alan Hayward has decided to step down
from his role as maintainer. Alan has been instrumental in keeping the Arm
ports robust and modern. Most notably, he championed the complex task of
implementing support for the Scalable Vector Extension (SVE), which required
significant changes to how GDB handles variable register sizes, something that
is used for SME to this day. Beyond SVE, he also enabled Pointer Authentication
support for AArch64. And his work on XML target descriptions and general
infrastructure refactoring have left the codebase in a much stronger position.
We thank Alan for his leadership and his many contributions to the project over
the years.
At the same time, I am pleased to announce that Thiago Bauermann has agreed to
step up as a new co-maintainer for AArch64 and Arm. Thiago is already a familiar
face in the community, having contributed extensively to GDB on PowerPC and,
more recently, AArch64. His recent work on MOPS, GCS and SME features have been
vital for keeping GDB aligned with the latest developments on AArch64.
Thiago has also contributed significant time reviewing patches from others,
something that is highly appreciated in the community.
Please join me in thanking Alan for his hard work and welcoming Thiago to
his new role. I have updated the gdb/MAINTAINERS file accordingly.
---
gdb/MAINTAINERS | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/gdb/MAINTAINERS b/gdb/MAINTAINERS
index ab06a8f8072..a6ac9f04099 100644
--- a/gdb/MAINTAINERS
+++ b/gdb/MAINTAINERS
@@ -319,8 +319,8 @@ resolving build issues. The Target/Architecture maintainer works with
the native maintainer when resolving ABI issues.
aarch64 --target=aarch64-elf
- Alan Hayward alan.hayward@arm.com
Luis Machado luis.machado.foss@gmail.com
+ Thiago Jung Bauermann thiago.bauermann@linaro.org
alpha --target=alpha-elf
@@ -331,8 +331,8 @@ the native maintainer when resolving ABI issues.
Shahab Vahedi list@vahedi.org
arm --target=arm-elf
- Alan Hayward alan.hayward@arm.com
Luis Machado luis.machado.foss@gmail.com
+ Thiago Jung Bauermann thiago.bauermann@linaro.org
avr --target=avr
@@ -872,6 +872,7 @@ Joel Brobecker (Global, Ada) brobecker@adacore.com
Doug Evans (Global) dje@google.com
Yao Qi (Global) qiyao@sourceware.org
Felix Willgerodt (amd64, i386) felix.willgerodt@gmail.com
+Alan Hayward (AArch64, arm) alan.hayward@arm.com
Folks that have been caught up in a paper trail:
--
2.43.0
next reply other threads:[~2026-03-27 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 16:09 Luis Machado [this message]
2026-03-27 19:43 ` Christophe Lyon
2026-03-29 17:01 ` Schimpe, Christina
2026-03-30 21:45 ` Luis
2026-03-31 1:25 ` 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=20260327160920.3809-1-luis.machado.foss@gmail.com \
--to=luis.machado.foss@gmail.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@linaro.org \
/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