Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/7] Shrink dwarf2/read.c and clean up lnp_state_machine
Date: Mon, 8 Sep 2025 13:18:25 -0400	[thread overview]
Message-ID: <61eda899-7828-41ba-a466-f40d4bc4c9c7@simark.ca> (raw)
In-Reply-To: <20250907-breakpoint-cu-expand-v1-0-dd2beef9d475@tromey.com>

On 9/7/25 3:29 PM, Tom Tromey wrote:
> This started with a patch to shrink dwarf2/read.c a bit, by moving
> lnp_state_machine to its own file.  Then I proceeded to clean up that
> code a tiny bit.
> 
> Regression tested on x86-64 Fedora 40.
> 
> Signed-off-by: Tom Tromey <tom@tromey.com>
> ---
> Tom Tromey (7):
>       Move lnp_state_machine to new file
>       Move compute_include_file_name earlier
>       Boolify line-program.c
>       Change dwarf_record_line_p to be a method
>       Add m_builder member to lnp_state_machine
>       Change dwarf_finish_line to be a method
>       Change dwarf_record_line_1 to be a method
> 
>  gdb/Makefile.in           |   1 +
>  gdb/dwarf2/line-program.c | 722 +++++++++++++++++++++++++++++++++++++
>  gdb/dwarf2/line-program.h |  47 +++
>  gdb/dwarf2/read.c         | 901 ++++------------------------------------------
>  gdb/dwarf2/read.h         |  31 ++
>  5 files changed, 874 insertions(+), 828 deletions(-)
> ---
> base-commit: 46ada32fc979550ad4f46792b74c182bb7232aeb
> change-id: 20250907-breakpoint-cu-expand-852f7e832aaa
> 
> Best regards,
> -- 
> Tom Tromey <tom@tromey.com>
> 

Thanks for doing this.  I think some comments would need updating, but
other than that it LGTM.  I don't think these changes warrant a new
version.

Approved-By: Simon Marchi <simon.marchi@efficios.com>

Simon

  parent reply	other threads:[~2025-09-08 17:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07 19:29 Tom Tromey
2025-09-07 19:29 ` [PATCH 1/7] Move lnp_state_machine to new file Tom Tromey
2025-09-08 16:04   ` Simon Marchi
2025-09-09  0:51     ` Tom Tromey
2025-09-09  0:52       ` Simon Marchi
2025-09-09  2:33         ` Eli Zaretskii
2025-09-09 23:25           ` Tom Tromey
2025-09-07 19:29 ` [PATCH 2/7] Move compute_include_file_name earlier Tom Tromey
2025-09-08 16:08   ` Simon Marchi
2025-09-09  0:46     ` Tom Tromey
2025-09-07 19:29 ` [PATCH 3/7] Boolify line-program.c Tom Tromey
2025-09-08 17:07   ` Simon Marchi
2025-09-09  0:48     ` Tom Tromey
2025-09-09  0:50       ` Simon Marchi
2025-09-09  1:11         ` Tom Tromey
2025-09-09 23:55           ` Tom Tromey
2025-09-10  1:51             ` Simon Marchi
2025-09-07 19:29 ` [PATCH 4/7] Change dwarf_record_line_p to be a method Tom Tromey
2025-09-07 19:29 ` [PATCH 5/7] Add m_builder member to lnp_state_machine Tom Tromey
2025-09-08 17:12   ` Simon Marchi
2025-09-07 19:29 ` [PATCH 6/7] Change dwarf_finish_line to be a method Tom Tromey
2025-09-08 17:14   ` Simon Marchi
2025-09-07 19:29 ` [PATCH 7/7] Change dwarf_record_line_1 " Tom Tromey
2025-09-08 17:17   ` Simon Marchi
2025-09-08 17:18 ` Simon Marchi [this message]
2025-09-09  0:54   ` [PATCH 0/7] Shrink dwarf2/read.c and clean up lnp_state_machine 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=61eda899-7828-41ba-a466-f40d4bc4c9c7@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /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