* [PATCH] Use string_file::release in some places
@ 2023-09-21 19:42 Tom Tromey
2023-09-22 20:42 ` Keith Seitz
0 siblings, 1 reply; 4+ messages in thread
From: Tom Tromey @ 2023-09-21 19:42 UTC (permalink / raw)
To: gdb-patches; +Cc: Tom Tromey
I found a few spots like:
string_file f;
std::string x = f.string ();
However, string_file::string returns a 'const std::string &'... so it
seems to me that this must be copying the string (? I find it hard to
reason about this in C++).
This patch changes these spots to use release() instead, which moves
the string.
---
gdb/breakpoint.c | 2 +-
gdb/top.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index d807ae3c9b5..f9b20a7d62d 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -7581,7 +7581,7 @@ bp_location::to_string () const
string_file stb;
ui_out_redirect_pop redir (current_uiout, &stb);
print_breakpoint_location (this->owner, this);
- return stb.string ();
+ return stb.release ();
}
/* Decrement reference count. If the reference count reaches 0,
diff --git a/gdb/top.c b/gdb/top.c
index 2322e55f1db..cbe14b01046 100644
--- a/gdb/top.c
+++ b/gdb/top.c
@@ -647,12 +647,12 @@ execute_fn_to_string (std::string &res, std::function<void(void)> fn,
catch (...)
{
/* Finally. */
- res = std::move (str_file.string ());
+ res = str_file.release ();
throw;
}
/* And finally. */
- res = std::move (str_file.string ());
+ res = str_file.release ();
}
/* See gdbcmd.h. */
--
2.40.1
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] Use string_file::release in some places
2023-09-21 19:42 [PATCH] Use string_file::release in some places Tom Tromey
@ 2023-09-22 20:42 ` Keith Seitz
2023-09-25 9:40 ` Lancelot SIX
2023-09-26 12:59 ` Tom Tromey
0 siblings, 2 replies; 4+ messages in thread
From: Keith Seitz @ 2023-09-22 20:42 UTC (permalink / raw)
To: Tom Tromey; +Cc: gdb-patches
On Thu, Sep 21, 2023 at 12:42 PM Tom Tromey via Gdb-patches
<gdb-patches@sourceware.org> wrote:
>
> I found a few spots like:
>
> string_file f;
> std::string x = f.string ();
>
> However, string_file::string returns a 'const std::string &'... so it
> seems to me that this must be copying the string (? I find it hard to
> reason about this in C++).
I admit, you now have me doubting everything I thought I remembered
on this subject! [TODO: reread the standard literature]
As far as I can tell, your assessment is at least consistent with what is
done elsewhere, e.g., location.c, ada-lang,c, and just about everywhere
else except the two locations you've identified in this patch.
Would symtab.c's symbol_to_info_string and valops.c:incomplete_type_hint
also qualify for similar treatment? They use addition assignment, so maybe
that alters the analogy?
In any case:
Reviewed-by: Keith Seitz <keiths@redhat.com>
Keith
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] Use string_file::release in some places
2023-09-22 20:42 ` Keith Seitz
@ 2023-09-25 9:40 ` Lancelot SIX
2023-09-26 12:59 ` Tom Tromey
1 sibling, 0 replies; 4+ messages in thread
From: Lancelot SIX @ 2023-09-25 9:40 UTC (permalink / raw)
To: Keith Seitz; +Cc: Tom Tromey, gdb-patches
On Fri, Sep 22, 2023 at 01:42:22PM -0700, Keith Seitz via Gdb-patches wrote:
> On Thu, Sep 21, 2023 at 12:42 PM Tom Tromey via Gdb-patches
> <gdb-patches@sourceware.org> wrote:
> >
> > I found a few spots like:
> >
> > string_file f;
> > std::string x = f.string ();
> >
> > However, string_file::string returns a 'const std::string &'... so it
> > seems to me that this must be copying the string (? I find it hard to
> > reason about this in C++).
Hi Tom and Keith,
I think your assessment is correct. Such case calls the string copy
operator[1] (i.e. `std::string::string (const std::string &)` - plus the
template expansion).
Same goes for the "return f.string ();" cases from a function returning
a std::string.
FWIW, the changes you made seems good to me.
Reviewed-by: Lancelot Six <lancelot.six@amd.com>
>
> I admit, you now have me doubting everything I thought I remembered
> on this subject! [TODO: reread the standard literature]
>
> As far as I can tell, your assessment is at least consistent with what is
> done elsewhere, e.g., location.c, ada-lang,c, and just about everywhere
> else except the two locations you've identified in this patch.
>
> Would symtab.c's symbol_to_info_string and valops.c:incomplete_type_hint
> also qualify for similar treatment? They use addition assignment, so maybe
> that alters the analogy?
In those cases, because the += operator is used, there is no move
semantics which can be leveraged[2]. This operator can only be used
with:
- const std::string & (what is currently used)
- char
- const char *
- std::initializer_list<char>
C++17 also adds string_view based option, but in all the cases we copy
the data from the argument.
Best,
Lancelot.
>
> In any case:
> Reviewed-by: Keith Seitz <keiths@redhat.com>
>
> Keith
>
[1] https://en.cppreference.com/w/cpp/language/copy_initialization
[2] https://en.cppreference.com/w/cpp/string/basic_string/operator%2B%3D
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] Use string_file::release in some places
2023-09-22 20:42 ` Keith Seitz
2023-09-25 9:40 ` Lancelot SIX
@ 2023-09-26 12:59 ` Tom Tromey
1 sibling, 0 replies; 4+ messages in thread
From: Tom Tromey @ 2023-09-26 12:59 UTC (permalink / raw)
To: Keith Seitz; +Cc: Tom Tromey, gdb-patches
>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
Keith> Would symtab.c's symbol_to_info_string and valops.c:incomplete_type_hint
Keith> also qualify for similar treatment? They use addition assignment, so maybe
Keith> that alters the analogy?
These two could accumulate all the text into a single string_file.
Maybe that would be slightly better.
Anyway I'm checking this in.
Tom
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-09-26 12:59 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-09-21 19:42 [PATCH] Use string_file::release in some places Tom Tromey
2023-09-22 20:42 ` Keith Seitz
2023-09-25 9:40 ` Lancelot SIX
2023-09-26 12:59 ` Tom Tromey
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).