public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/108210] New: error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model Date: Fri, 23 Dec 2022 13:37:07 +0000 [thread overview] Message-ID: <bug-108210-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210 Bug ID: 108210 Summary: error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: unlvsur at live dot com Target Milestone: --- /home/cqwrteur/toolchains_build/gcc/libstdc++-v3/src/c++20/tzdb.cc:565:5: error: 'mutex' does not name a type; did you mean 'minutes'? 565 | mutex infos_mutex; | ^~~~~ | minutes Win32 thread model does not provide mutex, lock_guard, and other threading mechanism. However. this can be implemented easily with win32 CriticalSection API. https://github.com/cppfastio/fast_io/blob/master/include/fast_io_hosted/threads/mutex/win32_critical_section.h
next reply other threads:[~2022-12-23 13:37 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-23 13:37 unlvsur at live dot com [this message] 2022-12-23 13:40 ` [Bug libstdc++/108210] " unlvsur at live dot com 2022-12-26 15:07 ` nightstrike at gmail dot com 2022-12-26 15:10 ` i.nixman at autistici dot org 2022-12-26 15:12 ` i.nixman at autistici dot org 2022-12-26 15:13 ` i.nixman at autistici dot org 2022-12-26 20:45 ` i.nixman at autistici dot org 2023-01-04 11:56 ` redi at gcc dot gnu.org 2023-01-04 13:38 ` redi at gcc dot gnu.org 2023-01-04 14:06 ` i.nixman at autistici dot 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-108210-4@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: 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).