From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: [pushed] gdb: remove stale comment and ctor in gdbarch_info
Date: Wed, 20 Dec 2023 10:52:13 -0500 [thread overview]
Message-ID: <20231220155214.199283-1-simon.marchi@efficios.com> (raw)
tdesc_data is not part of a union, since commit 4f3681cc3361 ("Fix thread's
gdbarch when SVE vector length changes"). Remove the stale comment and
constructor.
Change-Id: Ie895ce36614930e8bd9c4967174c8bf1b321c503
---
gdb/gdbarch.h | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/gdb/gdbarch.h b/gdb/gdbarch.h
index 82d42c9d2208..cc0be16c0417 100644
--- a/gdb/gdbarch.h
+++ b/gdb/gdbarch.h
@@ -232,12 +232,6 @@ struct gdbarch_list
struct gdbarch_info
{
- gdbarch_info ()
- /* Ensure the union is zero-initialized. Relies on the fact that there's
- no member larger than TDESC_DATA. */
- : tdesc_data ()
- {}
-
const struct bfd_arch_info *bfd_arch_info = nullptr;
enum bfd_endian byte_order = BFD_ENDIAN_UNKNOWN;
@@ -247,7 +241,7 @@ struct gdbarch_info
bfd *abfd = nullptr;
/* Architecture-specific target description data. */
- struct tdesc_arch_data *tdesc_data;
+ struct tdesc_arch_data *tdesc_data = nullptr;
enum gdb_osabi osabi = GDB_OSABI_UNKNOWN;
base-commit: 1c354ebcbacada00db94e8563eca2c73df2096b4
--
2.43.0
reply other threads:[~2023-12-20 15:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231220155214.199283-1-simon.marchi@efficios.com \
--to=simon.marchi@efficios.com \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).