From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH] [gdb/tdep] Eliminate ostringstream use from arc_check_tdesc_feature
Date: Sun, 22 Mar 2026 07:58:08 +0100 [thread overview]
Message-ID: <20260322065808.1127765-1-tdevries@suse.de> (raw)
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]);
}
arc_print (_("Error: Cannot find required register(s) %s "
- "in feature '%s'.\n"), reg_names.str ().c_str (),
+ "in feature '%s'.\n"), reg_names.c_str (),
feature->name.c_str ());
return false;
}
base-commit: d1cb5bd656a253cd69dbcd096f21f658cda697c7
--
2.51.0
next reply other threads:[~2026-03-22 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 6:58 Tom de Vries [this message]
2026-03-22 14:41 ` Simon Marchi
2026-03-22 16:10 ` 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=20260322065808.1127765-1-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