From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH] Increase size of main_type::nfields
Date: Wed, 11 Jan 2023 13:44:18 -0700 [thread overview]
Message-ID: <20230111204418.376620-1-tromey@adacore.com> (raw)
main_type::nfields is a 'short', and has been for many years. PR
c++/29985 points out that 'short' is too narrow for an enum that
contains more than 2^15 constants.
This patch bumps the size of 'nfields'. To verify that the field
isn't directly used, it is also renamed. Note that this does not
affect the size of main_type on x86-64 Fedora 36. And, if it does
have a negative effect somewhere, it's worth considering that types
could be shrunk more drastically by using subclasses for the different
codes.
I wasn't sure whether a test case for this would be desirable. It
would be a bit large.
---
gdb/gdb-gdb.py.in | 4 ++--
gdb/gdbtypes.h | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/gdb/gdb-gdb.py.in b/gdb/gdb-gdb.py.in
index dbc4d773e0b..95b7d84966f 100644
--- a/gdb/gdb-gdb.py.in
+++ b/gdb/gdb-gdb.py.in
@@ -261,8 +261,8 @@ class StructMainTypePrettyPrinter:
fields.append("flags = [%s]" % self.flags_to_string())
fields.append("owner = %s" % self.owner_to_string())
fields.append("target_type = %s" % self.val["m_target_type"])
- if self.val["nfields"] > 0:
- for fieldno in range(self.val["nfields"]):
+ if self.val["m_nfields"] > 0:
+ for fieldno in range(self.val["m_nfields"]):
fields.append(self.struct_field_img(fieldno))
if self.val["code"] == gdb.TYPE_CODE_RANGE:
fields.append(self.bounds_img())
diff --git a/gdb/gdbtypes.h b/gdb/gdbtypes.h
index a9abb0d8071..da1d0f79d1f 100644
--- a/gdb/gdbtypes.h
+++ b/gdb/gdbtypes.h
@@ -836,7 +836,7 @@ struct main_type
/* * Number of fields described for this type. This field appears
at this location because it packs nicely here. */
- short nfields;
+ int m_nfields;
/* * Name of this type, or NULL if none.
@@ -964,13 +964,13 @@ struct type
/* Get the number of fields of this type. */
int num_fields () const
{
- return this->main_type->nfields;
+ return this->main_type->m_nfields;
}
/* Set the number of fields of this type. */
void set_num_fields (int num_fields)
{
- this->main_type->nfields = num_fields;
+ this->main_type->m_nfields = num_fields;
}
/* Get the fields array of this type. */
--
2.38.1
next reply other threads:[~2023-01-11 20:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 20:44 Tom Tromey [this message]
2023-01-11 21:02 ` Simon Marchi
2023-01-11 21:28 ` Tom Tromey
2023-01-11 22:33 ` Simon Marchi
2023-01-12 19:14 ` Tom Tromey
2023-01-13 12:53 ` Pedro Alves
2023-01-27 14:49 ` Tom Tromey
2023-01-27 15:13 ` Tom Tromey
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=20230111204418.376620-1-tromey@adacore.com \
--to=tromey@adacore.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).