From: Tom Tromey <tromey@adacore.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] Introduce gdbsupport/cxx-thread.h and use it
Date: Thu, 02 Oct 2025 10:58:01 -0600 [thread overview]
Message-ID: <87jz1d8cme.fsf@tromey.com> (raw)
In-Reply-To: <dfea84c3-7560-4d1b-a78a-db846c9fd333@simark.ca> (Simon Marchi's message of "Wed, 1 Oct 2025 16:16:47 -0400")
Simon> Did you get a chance to validate your change on one of those toolchains
Simon> that don't have std::thread support?
I don't seem to have access to one any more. I thought perhaps my older
(Fedora 40) machine had a mingw toolchain without this support, but the
build still manages to define CXX_STD_THREAD.
Tom
next prev parent reply other threads:[~2025-10-02 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 18:57 [PATCH 0/3] Add compatibility definitions for C++ thread support Tom Tromey
2025-10-01 18:57 ` [PATCH 1/3] Remove an unused include Tom Tromey
2025-10-01 20:04 ` Simon Marchi
2025-10-02 12:59 ` Tom Tromey
2025-10-01 18:57 ` [PATCH 2/3] Don't rely on deduction in run-on-main-thread.c Tom Tromey
2025-10-01 18:57 ` [PATCH 3/3] Introduce gdbsupport/cxx-thread.h and use it Tom Tromey
2025-10-01 20:16 ` Simon Marchi
2025-10-02 16:58 ` Tom Tromey [this message]
2025-10-02 18:09 ` Tom Tromey
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=87jz1d8cme.fsf@tromey.com \
--to=tromey@adacore.com \
--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