public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jwakely.gcc at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/29966] Cannot build anymore for win32 thread model of gdb Date: Sat, 07 Jan 2023 21:58:44 +0000 [thread overview] Message-ID: <bug-29966-4717-dkxHcYiBw2@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29966-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29966 Jonathan Wakely <jwakely.gcc at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jwakely.gcc at gmail dot com --- Comment #12 from Jonathan Wakely <jwakely.gcc at gmail dot com> --- For libstdc++ I have no interest whatsoever in supporting Windows 98 and other dinosaurs. The win32 thread model that was previously completely non-functional now supports C++11 std::mutex etc. but only for "Windows Vista and Server 2008 or later" (to quote the comment in gthr-win32.h). If you define _WIN32_WINNT to an older value, you can't use std::mutex etc. That's not "something also wrong with gcc and libstdc++ too", it's just reality. So if GDB wants to use threads for a mingw target that uses --enable-threads=win32 (rather than --enable-thread=posix via libwinpthreads) then it needs to target Vista or Server 2008 or later. Otherwise, if it wants to target older versions of Windows, then it needs to not use std::mutex etc. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-07 21:58 UTC|newest] Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-06 0:14 [Bug build/29966] New: " euloanty at live dot com 2023-01-06 13:41 ` [Bug build/29966] " tromey at sourceware dot org 2023-01-07 0:53 ` euloanty at live dot com 2023-01-07 0:54 ` euloanty at live dot com 2023-01-07 3:41 ` tromey at sourceware dot org 2023-01-07 3:42 ` tromey at sourceware dot org 2023-01-07 18:14 ` euloanty at live dot com 2023-01-07 19:34 ` tromey at sourceware dot org 2023-01-07 19:44 ` euloanty at live dot com 2023-01-07 20:07 ` tromey at sourceware dot org 2023-01-07 21:13 ` euloanty at live dot com 2023-01-07 21:40 ` euloanty at live dot com 2023-01-07 21:58 ` jwakely.gcc at gmail dot com [this message] 2023-01-07 22:00 ` euloanty at live dot com 2023-01-07 22:04 ` jwakely.gcc at gmail dot com 2023-01-07 22:05 ` jwakely.gcc at gmail dot com 2023-01-07 22:08 ` jwakely.gcc at gmail dot com 2023-01-07 22:13 ` jwakely.gcc at gmail dot com 2023-01-08 1:16 ` tromey at sourceware dot org 2023-01-08 4:06 ` tromey at sourceware dot org 2023-01-09 14:48 ` tromey at sourceware dot org 2023-01-10 0:15 ` euloanty at live dot com 2023-01-10 0:45 ` jwakely.gcc at gmail dot com 2023-01-10 1:32 ` tromey at sourceware dot org 2023-01-10 6:57 ` euloanty at live dot com 2023-01-10 11:47 ` jwakely.gcc at gmail dot com 2023-01-10 14:06 ` tromey at sourceware dot org 2023-01-11 4:32 ` euloanty at live dot com 2023-01-11 6:19 ` tromey at sourceware dot org 2023-01-11 6:47 ` euloanty at live dot com 2023-01-11 9:48 ` jwakely.gcc at gmail dot com 2023-01-11 15:13 ` tromey at sourceware dot org 2023-01-11 18:00 ` cvs-commit at gcc dot gnu.org 2023-01-11 18:02 ` tromey at sourceware dot org 2023-01-12 14:59 ` cvs-commit at gcc dot gnu.org 2023-01-12 14:59 ` tromey at sourceware dot org 2023-01-13 7:07 ` euloanty at live dot com 2023-01-13 7:07 ` euloanty at live dot com 2023-01-13 12:33 ` jwakely.gcc at gmail dot com 2023-01-13 19:12 ` tromey at sourceware dot org 2023-01-13 19:14 ` euloanty at live dot com 2023-01-13 21:27 ` tromey at sourceware dot org 2023-01-13 21:31 ` euloanty at live dot com 2023-01-14 6:29 ` brobecker at gnat dot com 2023-01-14 6:36 ` brobecker at gnat dot com 2023-01-14 17:11 ` tromey at sourceware dot org 2023-01-14 17:45 ` jwakely.gcc at gmail dot com 2023-01-14 17:52 ` jwakely.gcc at gmail dot com 2023-01-14 17:58 ` jwakely.gcc at gmail dot com 2023-01-18 16:55 ` tromey at sourceware dot org 2023-01-19 1:28 ` euloanty at live dot com 2023-01-19 16:49 ` tromey at sourceware dot org 2023-01-23 10:25 ` jwakely.gcc at gmail dot com 2023-01-23 10:54 ` jwakely.gcc at gmail dot com 2023-01-27 19:32 ` tromey at sourceware dot org 2023-01-28 2:27 ` euloanty at live dot com 2023-01-28 2:28 ` euloanty at live dot com 2023-01-28 2:30 ` euloanty at live dot com 2023-01-28 4:00 ` euloanty at live dot com 2023-01-28 10:08 ` jwakely.gcc at gmail dot com 2023-01-28 11:48 ` mark at klomp dot org 2023-01-29 3:41 ` tromey at sourceware dot org 2023-01-29 3:43 ` euloanty at live dot com 2023-01-29 3:44 ` euloanty at live dot com 2023-01-29 3:45 ` euloanty at live dot com 2023-01-29 3:54 ` euloanty at live dot com 2023-01-29 11:44 ` brobecker at gnat dot com 2023-01-29 13:27 ` mark at klomp dot org 2023-01-30 1:21 ` tromey at sourceware dot org 2024-12-14 15:39 ` euloanty at live dot com 2024-12-14 16:26 ` tromey at sourceware dot org 2024-12-15 2:28 ` euloanty at live dot com 2024-12-15 2:30 ` euloanty at live dot com 2024-12-15 17:03 ` ssbssa at sourceware dot org 2024-12-15 21:19 ` simon.marchi at polymtl dot ca 2024-12-16 7:27 ` euloanty at live dot com
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-29966-4717-dkxHcYiBw2@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).