public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108326] Question about definitions in c++config.h for gcc13 20221229
Date: Sat, 07 Jan 2023 15:44:39 +0000 [thread overview]
Message-ID: <bug-108326-4-UxhZ2NyAea@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108326-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108326
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jamaika from comment #0)
> Amateur questions
> I know that creating exe files two years ago with <thread>, <mutex> with
> _GLIBCXX_HAS_GTHREADS definition was impossible.
This is just nonsense, so I assume you mean impossible when using mingw without
libwinpthread. It works fine on most targets, and for mingw-w64 when using
libwinpthread.
next prev parent reply other threads:[~2023-01-07 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 6:18 [Bug c++/108326] New: " lukaszcz18 at wp dot pl
2023-01-07 11:25 ` [Bug libstdc++/108326] " pinskia at gcc dot gnu.org
2023-01-07 15:42 ` redi at gcc dot gnu.org
2023-01-07 15:44 ` redi at gcc dot gnu.org [this message]
2023-01-08 10:22 ` lukaszcz18 at wp dot pl
2023-01-09 9:56 ` redi at gcc dot gnu.org
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=bug-108326-4-UxhZ2NyAea@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).