From: Tankut Baris Aktemur <tankutbaris.aktemur@amd.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 1/2] gdb: remove dead code in make_pointer_type and make_reference_type
Date: Mon, 3 Aug 2026 16:35:30 +0200 [thread overview]
Message-ID: <20260803143531.2958552-1-tankutbaris.aktemur@amd.com> (raw)
At the end of `make_pointer_type` and `make_reference_type`, GDB
updates the length of every type in the chain. This is practically
dead code, because if we reach this point, we must have allocated a
new type. After a new allocation, the chain contains only the
newly-created type itself. See in `type_allocator::new_type ()`:
type->chain = type; /* Chain back to itself. */
That is, we always have `ntype == ntype->chain`. Therefore, the loop
can never be entered. Remove it.
In `make_reference_type`, we also remove `*reftype = ntype;`, because
a few lines above the assignment was already made. This is repeated
code.
---
gdb/gdbtypes.c | 21 ---------------------
1 file changed, 21 deletions(-)
diff --git a/gdb/gdbtypes.c b/gdb/gdbtypes.c
index 9098727959e..2dda175237c 100644
--- a/gdb/gdbtypes.c
+++ b/gdb/gdbtypes.c
@@ -367,8 +367,6 @@ type *
make_pointer_type (type *type)
{
struct type *ntype; /* New type */
- struct type *chain;
-
ntype = type->pointer_type;
if (ntype)
@@ -388,14 +386,6 @@ make_pointer_type (type *type)
gdbarch_address_to_pointer. */
ntype->set_is_unsigned (true);
- /* Update the length of all the other variants of this type. */
- chain = ntype->chain;
- while (chain != ntype)
- {
- chain->set_length (ntype->length ());
- chain = chain->chain;
- }
-
return ntype;
}
@@ -415,7 +405,6 @@ make_reference_type (type *type, type_code refcode)
{
struct type *ntype; /* New type */
struct type **reftype;
- struct type *chain;
gdb_assert (refcode == TYPE_CODE_REF || refcode == TYPE_CODE_RVALUE_REF);
@@ -439,16 +428,6 @@ make_reference_type (type *type, type_code refcode)
ntype->set_length (gdbarch_ptr_bit (type->arch ()) / TARGET_CHAR_BIT);
ntype->set_code (refcode);
- *reftype = ntype;
-
- /* Update the length of all the other variants of this type. */
- chain = ntype->chain;
- while (chain != ntype)
- {
- chain->set_length (ntype->length ());
- chain = chain->chain;
- }
-
return ntype;
}
--
2.53.0
next reply other threads:[~2026-08-03 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 14:35 Tankut Baris Aktemur [this message]
2026-08-03 14:35 ` [PATCH 2/2] gdb: do minor code modernization " Tankut Baris Aktemur
2026-08-03 14:51 ` Simon Marchi
2026-08-03 14:50 ` [PATCH 1/2] gdb: remove dead code " Simon Marchi
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=20260803143531.2958552-1-tankutbaris.aktemur@amd.com \
--to=tankutbaris.aktemur@amd.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