From: Matthieu Longo <matthieu.longo@arm.com>
To: <gdb-patches@sourceware.org>
Cc: Alan Hayward <alan.hayward@arm.com>,
Luis Machado <luis.machado@linaro.org>,
Luis Machado <luis.machado.foss@gmail.com>,
Matthieu Longo <matthieu.longo@arm.com>
Subject: [PATCH v1] gdb/aarch64: fix typo gcs_availabe
Date: Fri, 5 Jun 2026 17:48:01 +0100 [thread overview]
Message-ID: <20260605164801.1244059-1-matthieu.longo@arm.com> (raw)
---
gdb/aarch64-linux-tdep.c | 6 +++---
gdb/arch/aarch64.h | 1 +
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/gdb/aarch64-linux-tdep.c b/gdb/aarch64-linux-tdep.c
index ae21b029276..f11eccc1bc1 100644
--- a/gdb/aarch64-linux-tdep.c
+++ b/gdb/aarch64-linux-tdep.c
@@ -261,7 +261,7 @@ struct aarch64_linux_sigframe
bool zt_available = false;
/* True if we have a GCS entry in the signal context, false otherwise. */
- bool gcs_availabe = false;
+ bool gcs_available = false;
/* The Guarded Control Stack Pointer Register. */
uint64_t gcspr;
/* Flags indicating which GCS features are enabled for the thread. */
@@ -584,7 +584,7 @@ aarch64_linux_read_signal_frame_info (const frame_info_ptr &this_frame,
signal_frame.gcs_features_enabled
= extract_unsigned_integer (buf, byte_order);
- signal_frame.gcs_availabe = true;
+ signal_frame.gcs_available = true;
section += size;
break;
}
@@ -787,7 +787,7 @@ aarch64_linux_sigframe_init (const struct tramp_frame *self,
/* Restore the GCS registers, if the target supports it and if there is
an entry for them. */
- if (signal_frame.gcs_availabe && tdep->has_gcs_linux ())
+ if (signal_frame.gcs_available && tdep->has_gcs_linux ())
{
/* Restore GCSPR. */
trad_frame_set_reg_value (this_cache, tdep->gcs_reg_base,
diff --git a/gdb/arch/aarch64.h b/gdb/arch/aarch64.h
index c9a89ac4098..cf7318cbe74 100644
--- a/gdb/arch/aarch64.h
+++ b/gdb/arch/aarch64.h
@@ -97,6 +97,7 @@ namespace std
/* SME2 feature. */
h = h << 1 | features.sme2;
+ /* GCS feature. */
h = h << 1 | features.gcs;
h = h << 1 | features.gcs_linux;
--
2.54.0
next reply other threads:[~2026-06-05 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 16:48 Matthieu Longo [this message]
2026-06-07 2:29 ` Thiago Jung Bauermann
2026-06-08 13:52 ` Tom de Vries
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=20260605164801.1244059-1-matthieu.longo@arm.com \
--to=matthieu.longo@arm.com \
--cc=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado.foss@gmail.com \
--cc=luis.machado@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