public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>
Subject: Re: [PATCH 0/7] [gdb/build] Fix -std=c++20 issues
Date: Wed, 16 Aug 2023 12:27:56 -0600	[thread overview]
Message-ID: <87sf8iyh8z.fsf@tromey.com> (raw)
In-Reply-To: <20230815181309.8595-1-tdevries@suse.de> (Tom de Vries via Gdb-patches's message of "Tue, 15 Aug 2023 20:13:02 +0200")

>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:

Tom> I tried building gdb using -std=c++20, an ran into a few issues.
Tom> This series contains fixes for most of them.

Thanks for doing this.  I read these & sent one comment.
The rest look ok to me.

Tom> But the other one, in remote_target::thread_info_to_thread_handle remains
Tom> unfixed:
Tom> ...
Tom> gdb::byte_vector
Tom> remote_target::thread_info_to_thread_handle (struct thread_info *tp)
Tom> {
Tom>   remote_thread_info *priv = get_remote_thread_info (tp);
Tom>   return priv->thread_handle;

First, I wonder if we even care about this copying.

But if we do, it could return a const reference and linux-thread-db
could be modified to cache the byte_vector in thread_db_thread_info.

Tom

  parent reply	other threads:[~2023-08-16 20:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 18:13 Tom de Vries
2023-08-15 18:13 ` [PATCH 1/7] [gdb/build, c++20] Fix Wdeprecated-enum-enum-conversion Tom de Vries
2023-08-15 18:13 ` [PATCH 2/7] [gdb/build, c++20] Stop using deprecated is_pod Tom de Vries
2023-08-15 18:13 ` [PATCH 3/7] [gdb/build, c++20] Fix DISABLE_COPY_AND_ASSIGN use in ui_out_emit_type Tom de Vries
2023-08-15 18:13 ` [PATCH 4/7] [gdb/build, c++20] Fix deprecated implicit capture of this Tom de Vries
2023-08-15 18:13 ` [PATCH 5/7] [gdb/build, c++20] Fix invalid conversion in test_symbols Tom de Vries
2023-08-15 18:13 ` [PATCH 6/7] [gdb/build] Return reference in target_read_auxv Tom de Vries
2023-08-16 18:23   ` Tom Tromey
2023-08-15 18:13 ` [PATCH 7/7] [gdb/build, c++20] Handle deprecated std::allocator::construct Tom de Vries
2023-08-16 18:27 ` Tom Tromey [this message]
2023-08-21 11:04   ` [PATCH 0/7] [gdb/build] Fix -std=c++20 issues 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=87sf8iyh8z.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).