public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/95392] [11 Regression] Build failure on MinGW
Date: Mon, 01 Jun 2020 23:14:22 +0000	[thread overview]
Message-ID: <bug-95392-4-IbSuubEJZl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95392-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 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:cd3f067b82a1331f5fb695879ba5c3d9bb2cca3a

commit r11-777-gcd3f067b82a1331f5fb695879ba5c3d9bb2cca3a
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Jun 2 00:07:05 2020 +0100

    libstdc++: Fix filesystem::u8path for mingw targets (PR 95392)

    When I refactored filesystem::path string conversions in
    r11-587-584d52b088f9fcf78704b504c3f1f07e17c1cded I failed to update the
    mingw-specific code in filesystem::u8path, causing a bootstrap failure.

    This fixes it, and further refactors the mingw-specific code along the
    same lines as the previous commit. All conversions from UTF-8 strings to
    wide strings now use the same helper function, __wstr_from_utf8.

            PR libstdc++/95392
            * include/bits/fs_path.h (path::_S_to_string): Move to
            namespace-scope and rename to ...
            (__detail::__string_from_range): ... this.
            [WINDOWS] (__detail::__wstr_from_utf8): New function template to
            convert a char sequence containing UTF-8 to wstring.
            (path::_S_convert(Iter, Iter)): Adjust call to _S_to_string.
            (path::_S_convert_loc(Iter, Iter, const locale&)): Likewise.
            (u8path(InputIterator, InputIterator)) [WINDOWS]: Use
            __string_from_range to obtain a contiguous range and
            __wstr_from_utf8 to obtain a wide string.
            (u8path(const Source&)) [WINDOWS]: Use __effective_range to
            obtain a contiguous range and __wstr_from_utf8 to obtain a wide
            string.
            (path::_S_convert(const _EcharT*, const _EcharT)) [WINDOWS]:
            Use __wstr_from_utf8.

  parent reply	other threads:[~2020-06-01 23:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 17:01 [Bug libstdc++/95392] New: " markus.boeck02 at gmail dot com
2020-05-28 17:37 ` [Bug libstdc++/95392] [11 Regression] " redi at gcc dot gnu.org
2020-05-28 17:38 ` redi at gcc dot gnu.org
2020-06-01 23:14 ` cvs-commit at gcc dot gnu.org [this message]
2020-06-01 23:15 ` 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-95392-4-IbSuubEJZl@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).