[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

[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

[unlvsur at live dot com]

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

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

[unlvsur at live dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210

cqwrteur <unlvsur at live dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |unlvsur at live dot com

--- Comment #1 from cqwrteur <unlvsur at live dot com> ---
Created attachment 54152
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54152&action=edit
config

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

[nightstrike at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210

nightstrike <nightstrike at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |i.nixman at autistici dot org,
                   |                            |nightstrike at gmail dot com

--- Comment #2 from nightstrike <nightstrike at gmail dot com> ---
Is this before or after this patch set was applied?

https://gcc.gnu.org/pipermail/gcc-patches/2022-December/609116.html

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

[i.nixman at autistici dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210

--- Comment #3 from niXman <i.nixman at autistici dot org> ---
(In reply to cqwrteur from comment #0)
> /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

please provide the configure's options you used.

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

[i.nixman at autistici dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210

--- Comment #4 from niXman <i.nixman at autistici dot org> ---
(In reply to nightstrike from comment #2)
> Is this before or after this patch set was applied?
> 
> https://gcc.gnu.org/pipermail/gcc-patches/2022-December/609116.html

I think it can be so because of unspecified `--enable-libstdcxx-threads=yes`
option.

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

[i.nixman at autistici dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210

--- Comment #5 from niXman <i.nixman at autistici dot org> ---
(In reply to niXman from comment #4)
> (In reply to nightstrike from comment #2)
> > Is this before or after this patch set was applied?
> > 
> > https://gcc.gnu.org/pipermail/gcc-patches/2022-December/609116.html
> 
> I think it can be so because of unspecified `--enable-libstdcxx-threads=yes`
> option.

will try to build now without that option.

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

[i.nixman at autistici dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210

--- Comment #6 from niXman <i.nixman at autistici dot org> ---
(In reply to niXman from comment #5)
> (In reply to niXman from comment #4)
> > (In reply to nightstrike from comment #2)
> > > Is this before or after this patch set was applied?
> > > 
> > > https://gcc.gnu.org/pipermail/gcc-patches/2022-December/609116.html
> > 
> > I think it can be so because of unspecified `--enable-libstdcxx-threads=yes`
> > option.
> 
> will try to build now without that option.

it built successfully.

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2023-01-04
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |WAITING

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Probably a dup of PR 108225 i.e. expecting --enable-threads=win32 to provide
std::mutex without _WIN32_WINNT >= 0x0600

But it isn't provided, because the win32 model doesn't support C++11 threading
for ancient versions:

/* Condition variables are supported on Vista and Server 2008 or later.  */

[Bug libstdc++/108210] error: 'mutex' does not name a type; did you mean 'minutes'? for x86_64-w64-mingw32 target with win32 thread model

[i.nixman at autistici dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108210

--- Comment #8 from niXman <i.nixman at autistici dot org> ---
(In reply to Jonathan Wakely from comment #7)
> Probably a dup of PR 108225 i.e. expecting --enable-threads=win32 to provide
> std::mutex without _WIN32_WINNT >= 0x0600

yep, sure!

> But it isn't provided, because the win32 model doesn't support C++11
> threading for ancient versions:
> 
> /* Condition variables are supported on Vista and Server 2008 or later.  */

right.

it's strange that the same person posted the same issue twice on two diff BR...