From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/tdep] Eliminate ostringstream use from arc_check_tdesc_feature
Date: Sun, 22 Mar 2026 17:10:01 +0100 [thread overview]
Message-ID: <94cc49b3-0a14-4334-a348-f525a3d96cd0@suse.de> (raw)
In-Reply-To: <e61f04b4-652c-42d5-91a7-776434703156@simark.ca>
On 3/22/26 3:41 PM, Simon Marchi wrote:
> On 3/22/26 2:58 AM, Tom de Vries wrote:
>> We generally avoid C++ streams in GDB sources [1].
>>
>> Remove an instance of std::ostringstream in arc_check_tdesc_feature.
>>
>> While we're at it, fix an array index bug:
>> ...
>> - reg_names << " or '" << reg.names[0] << "'";
>> + string_appendf (reg_names, " or '%s'", reg.names[i]);
>> ...
>>
>> Tested on x86_64-linux, using a trigger patch:
>> ...
>> - if (!found && reg.required_p)
>> + if (true || (!found && reg.required_p))
>> ...
>> and doing "maint selftest" and observing the output:
>> ...
>> Running selftest unpack_field_as_long::ARC600.
>> Error: Cannot find required register(s) 'r0' in feature 'org.gnu.gdb.arc.core'.
>> Error: Cannot find required register(s) 'pc' in feature 'org.gnu.gdb.arc.aux'.
>> ...
>>
>> [1] https://sourceware.org/pipermail/gdb-patches/2026-March/226117.html
>> ---
>> gdb/arc-tdep.c | 9 ++++-----
>> 1 file changed, 4 insertions(+), 5 deletions(-)
>>
>> diff --git a/gdb/arc-tdep.c b/gdb/arc-tdep.c
>> index ff283014e52..4936a5c8fbb 100644
>> --- a/gdb/arc-tdep.c
>> +++ b/gdb/arc-tdep.c
>> @@ -44,7 +44,6 @@
>>
>> /* Standard headers. */
>> #include <algorithm>
>> -#include <sstream>
>>
>> /* The frame unwind cache for ARC. */
>>
>> @@ -2100,16 +2099,16 @@ arc_check_tdesc_feature (struct tdesc_arch_data *tdesc_data,
>>
>> if (!found && reg.required_p)
>> {
>> - std::ostringstream reg_names;
>> + std::string reg_names;
>> for (std::size_t i = 0; i < reg.names.size(); ++i)
>> {
>> if (i == 0)
>> - reg_names << "'" << reg.names[0] << "'";
>> + string_appendf (reg_names, "'%s'", reg.names[0]);
>> else
>> - reg_names << " or '" << reg.names[0] << "'";
>> + string_appendf (reg_names, " or '%s'", reg.names[i]);
>
Hi Simon,
thanks for the review.
> Looks like you fixed a bug here (0 -> i).
Yes, that's what I meant by "fix an array index bug".
Thanks,
- Tom
> Approved-By: Simon Marchi <simon.marchi@efficios.com>
>
> Simon
prev parent reply other threads:[~2026-03-22 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 6:58 Tom de Vries
2026-03-22 14:41 ` Simon Marchi
2026-03-22 16:10 ` Tom de Vries [this message]
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=94cc49b3-0a14-4334-a348-f525a3d96cd0@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.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