public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/93244] std::filesystem::path::generic_string doesn't convert the first slash on Windows Date: Thu, 12 Mar 2020 18:47:43 +0000 [thread overview] Message-ID: <bug-93244-4-n8ZEj358jU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93244-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93244 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org --- Comment #12 from Martin Liška <marxin at gcc dot gnu.org> --- commit r9-8365-g362c8772e7779d9e4730e2e51628ccaadce98bd0 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Mar 12 17:39:04 2020 +0000 libstdc++: Ensure root-dir converted to forward slash (PR93244) Backport from mainline 2020-01-13 Jonathan Wakely <jwakely@redhat.com> PR libstdc++/93244 * include/bits/fs_path.h (path::generic_string<C,A>) [_GLIBCXX_FILESYSTEM_IS_WINDOWS]: Convert root-dir to forward-slash. * testsuite/27_io/filesystem/path/generic/generic_string.cc: Check root-dir is converted to forward slash in generic pathname. * testsuite/27_io/filesystem/path/generic/utf.cc: New test. * testsuite/27_io/filesystem/path/generic/wchar_t.cc: New test.
next prev parent reply other threads:[~2020-03-12 18:47 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93244-4@http.gcc.gnu.org/bugzilla/> 2020-03-12 11:58 ` jakub at gcc dot gnu.org 2020-03-12 17:40 ` redi at gcc dot gnu.org 2020-03-12 18:47 ` marxin at gcc dot gnu.org [this message] 2020-05-12 8:02 ` cvs-commit at gcc dot gnu.org 2020-05-12 8:15 ` marxin 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-93244-4-n8ZEj358jU@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).