From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org, Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH 2/6] gdb/testsuite/dwarf: convert _section proc to use parse_options
Date: Wed, 19 Nov 2025 08:53:37 -0700 [thread overview]
Message-ID: <87v7j6qari.fsf@tromey.com> (raw)
In-Reply-To: <20251107211041.520697-3-simon.marchi@efficios.com> (Simon Marchi's message of "Fri, 7 Nov 2025 16:10:13 -0500")
>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
I meant to send this last week but forgot.
Simon> - proc _section {name {flags ""} {type ""}} {
Simon> - if {$name == ".debug_str"} {
Simon> - # Hard-code this because it's always desirable.
Simon> - _emit " .section $name, \"MS\", %progbits, 1"
Simon> - } elseif {$flags == "" && $type == ""} {
Simon> - _emit " .section $name"
Simon> - } elseif {$type == ""} {
Simon> - _emit " .section $name, \"$flags\""
Simon> - } else {
Simon> - _emit " .section $name, \"$flags\", %$type"
This code ignores flags and type if name is .debug_str, but the
replacement code:
Simon> + if { $name == ".debug_str" } {
Simon> + # Hard-code this because it's always desirable.
Simon> + append directive ", \"MS\", %progbits, 1"
Simon> + }
Simon> +
Simon> + if { $flags != "" } {
Simon> + append directive ",\"$flags\""
Simon> + }
Simon> +
Simon> + if { $type != "" } {
Simon> + # Can't specify a type without flags.
Simon> + if { $flags == "" } {
Simon> + append directive ", \"\""
Simon> + }
Simon> +
Simon> + append directive ", %$type"
Simon> + }
... does not.
I think the old code was clearer in this regard. I didn't read forward
in the series to see if this restructuring helps newer code though.
Anyway this change should be addressed.
Tom
next prev parent reply other threads:[~2025-11-19 15:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 21:10 [PATCH 0/6] Type unit + split DWARF fixes (PR 33307) Simon Marchi
2025-11-07 21:10 ` [PATCH 1/6] gdb/testsuite/dwarf: use single abbrev table in .dwo files Simon Marchi
2025-11-10 20:14 ` Simon Marchi
2025-11-18 13:32 ` Andrew Burgess
2025-11-18 16:50 ` Simon Marchi
2025-11-18 16:55 ` Andrew Burgess
2025-11-18 17:20 ` Simon Marchi
2025-11-19 16:05 ` Tom Tromey
2025-11-19 20:21 ` Simon Marchi
2025-11-07 21:10 ` [PATCH 2/6] gdb/testsuite/dwarf: convert _section proc to use parse_options Simon Marchi
2025-11-19 10:59 ` Andrew Burgess
2025-11-19 15:53 ` Tom Tromey [this message]
2025-11-19 20:40 ` Simon Marchi
2025-11-19 21:03 ` Tom Tromey
2025-11-07 21:10 ` [PATCH 3/6] gdb/testsuite/dwarf: emit type unit sections as COMDAT Simon Marchi
2025-11-19 11:43 ` Andrew Burgess
2025-11-07 21:10 ` [PATCH 4/6] gdb/dwarf: when in dwarf2_cu, read addr_size from dwarf2_cu::header Simon Marchi
2025-11-19 14:30 ` Andrew Burgess
2025-11-19 20:46 ` Simon Marchi
2025-11-19 16:11 ` Tom Tromey
2025-11-19 20:51 ` Simon Marchi
2025-11-07 21:10 ` [PATCH 5/6] gdb/dwarf: store addr/offset/ref_addr sizes in dwarf2_per_cu Simon Marchi
2025-11-19 14:42 ` Andrew Burgess
2025-11-19 16:14 ` Tom Tromey
2025-11-21 19:54 ` Simon Marchi
2025-11-21 21:25 ` Tom Tromey
2025-11-07 21:10 ` [PATCH 6/6] gdb/dwarf: use dwarf2_per_cu::ref_addr_size in one spot Simon Marchi
2025-11-19 14:44 ` Andrew Burgess
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=87v7j6qari.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
--cc=simon.marchi@polymtl.ca \
/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