Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 07/12] [gdb] Fix redundant struct typedefs
Date: Tue, 16 Jun 2026 08:22:52 +0200	[thread overview]
Message-ID: <20260616062257.3164438-8-tdevries@suse.de> (raw)
In-Reply-To: <20260616062257.3164438-1-tdevries@suse.de>

Convert "typedef struct foo { ... } foo" into "struct foo { ... }".

Generated by a script written by Claude Code.
---
 gdb/procfs.c            | 4 ++--
 gdbserver/tracepoint.cc | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/gdb/procfs.c b/gdb/procfs.c
index 64a71ea2883..8d96bf588da 100644
--- a/gdb/procfs.c
+++ b/gdb/procfs.c
@@ -224,7 +224,7 @@ procfs_target::auxv_parse (const gdb_byte **readptr,
 #define STATUS_PROC_NAME_FMT "/proc/%d/status"
 #define MAX_PROC_NAME_SIZE sizeof("/proc/999999/lwp/0123456789/lwpstatus")
 
-typedef struct procinfo {
+struct procinfo {
   struct procinfo *next;
   int pid;			/* Process ID    */
   int tid;			/* Thread/LWP id */
@@ -253,7 +253,7 @@ typedef struct procinfo {
   int gregs_valid  : 1;
   int fpregs_valid : 1;
   int threads_valid: 1;
-} procinfo;
+};
 
 /* Function prototypes for procinfo module: */
 
diff --git a/gdbserver/tracepoint.cc b/gdbserver/tracepoint.cc
index e5d95726422..593dca65f76 100644
--- a/gdbserver/tracepoint.cc
+++ b/gdbserver/tracepoint.cc
@@ -5094,7 +5094,7 @@ fast_tracepoint_from_ipa_tpoint_address (CORE_ADDR ipa_tpoint_obj)
 /* The type of the object that is used to synchronize fast tracepoint
    collection.  */
 
-typedef struct collecting_t
+struct collecting_t
 {
   /* The fast tracepoint number currently collecting.  */
   uintptr_t tpoint;
@@ -5107,7 +5107,7 @@ typedef struct collecting_t
      register, which is readable with a single insn on several
      architectures.  */
   uintptr_t thread_area;
-} collecting_t;
+};
 
 #ifndef IN_PROCESS_AGENT
 
-- 
2.51.0


  parent reply	other threads:[~2026-06-16  6:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16  6:22 [PATCH 00/12] [gdb] Use using instead of typedef some more Tom de Vries
2026-06-16  6:22 ` [PATCH 01/12] [gdb] Use using instead of typedef some more (part 1) Tom de Vries
2026-06-26 15:40   ` Tom Tromey
2026-06-16  6:22 ` [PATCH 02/12] [gdb] Use using instead of typedef some more (part 2) Tom de Vries
2026-06-16  6:22 ` [PATCH 03/12] [gdb] Use using instead of typedef some more (part 3) Tom de Vries
2026-06-26 15:49   ` Tom Tromey
2026-06-16  6:22 ` [PATCH 04/12] [gdb] Convert function pointer typedefs to using Tom de Vries
2026-06-16  6:22 ` [PATCH 05/12] [gdb] Convert template " Tom de Vries
2026-06-16  6:22 ` [PATCH 06/12] [gdb] Convert function " Tom de Vries
2026-06-16  6:22 ` Tom de Vries [this message]
2026-06-16  6:22 ` [PATCH 08/12] [gdb] Convert anonymous struct typedefs Tom de Vries
2026-06-16  6:22 ` [PATCH 09/12] [gdb] Convert typedef of named struct Tom de Vries
2026-06-26 16:04   ` Tom Tromey
2026-06-16  6:22 ` [PATCH 10/12] [gdb] convert struct pointer typedefs Tom de Vries
2026-06-16  6:22 ` [PATCH 11/12] [gdb] Convert typedef on separate line Tom de Vries
2026-06-16  6:22 ` [PATCH 12/12] [gdb] Use using in compat_x32_clock_t typedef Tom de Vries
2026-06-26 16:05 ` [PATCH 00/12] [gdb] Use using instead of typedef some more Tom Tromey
2026-07-13 13:07   ` 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=20260616062257.3164438-8-tdevries@suse.de \
    --to=tdevries@suse.de \
    --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