[Bug libstdc++/102743] New: build failure for i686-w64-mingw32 target because of patch yesterday

[Bug libstdc++/102743] New: build failure for i686-w64-mingw32 target because of patch yesterday

[unlvsur at live dot com]

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

            Bug ID: 102743
           Summary: build failure for i686-w64-mingw32 target because of
                    patch yesterday
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: unlvsur at live dot com
  Target Milestone: ---

Created attachment 51599
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51599&action=edit
error message

[Bug libstdc++/102743] [12 Regression] build failure for i686-w64-mingw32 target because of patch yesterday

[pinskia at gcc dot gnu.org]

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|build failure for           |[12 Regression] build
                   |i686-w64-mingw32 target     |failure for
                   |because of patch yesterday  |i686-w64-mingw32 target
                   |                            |because of patch yesterday
           Keywords|                            |build
   Target Milestone|---                         |12.0

[Bug libstdc++/102743] [12 Regression] build failure for i686-w64-mingw32 target because of patch yesterday

[redi at gcc dot gnu.org]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
           Assignee|unassigned at gcc dot gnu.org      |redi at gcc dot gnu.org
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2021-10-14

[Bug libstdc++/102743] [12 Regression] build failure for i686-w64-mingw32 target because of patch yesterday

[cvs-commit at gcc dot gnu.org]

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:5e3f88838994b67580594c4679c839fff7cdeba0

commit r12-4404-g5e3f88838994b67580594c4679c839fff7cdeba0
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Oct 14 13:20:57 2021 +0100

    libstdc++: Fix brainwrong in path::_S_convert(T) [PR102743]

    This function was supposed to check whether the parameter's value type
    is the same as path::value_type, and therefore needs no conversion.
    Instead it checks whether the parameter is the same as its own value
    type, which is never true. This means we incorrectly return a string
    view for the case where T is path::string_type, instead of just
    returning the string itself. The only place that happens is
    path::_S_convert_loc for Windows, where we call _S_convert with a
    std::wstring rvalue.

    This fixes the condition in _S_convert(T).

    libstdc++-v3/ChangeLog:

            PR libstdc++/102743
            * include/bits/fs_path.h (path::_S_convert(T)): Fix condition
            for returning the same string unchanged.

[Bug libstdc++/102743] [12 Regression] build failure for i686-w64-mingw32 target because of patch yesterday

[redi at gcc dot gnu.org]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|jwakely at redhat dot com          |
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed - sorry about that.