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++/88881] std::filesystem::status gives bad results on mingw32 Date: Thu, 30 Jun 2022 13:16:53 +0000 [thread overview] Message-ID: <bug-88881-4-BJUnMlRczn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-88881-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88881 --- Comment #24 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:6c96b14a19a9e6c365eacc59868a866b99f9786d commit r13-1365-g6c96b14a19a9e6c365eacc59868a866b99f9786d Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Jun 28 15:56:30 2022 +0100 libstdc++: Fix experimental::filesystem::status on Windows [PR88881] Although the Filesystem TS isn't properly supported on Windows (unlike the C++17 Filesystem lib), most tests do pass. Two of the failures are due to PR 88881 which was only fixed for std::filesystem not the TS. This applies the fix to the TS implementation too. libstdc++-v3/ChangeLog: PR libstdc++/88881 * src/filesystem/ops.cc (has_trailing_slash): New helper function. (fs::status): Strip trailing slashes. (fs::symlink_status): Likewise. * testsuite/experimental/filesystem/operations/temp_directory_path.cc: Clean the environment before each test and use TMP instead of TMPDIR so the test passes on Windows.
next prev parent reply other threads:[~2022-06-30 13:16 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-88881-4@http.gcc.gnu.org/bugzilla/> 2020-11-27 13:55 ` redi at gcc dot gnu.org 2020-11-27 14:00 ` redi at gcc dot gnu.org 2020-11-27 14:01 ` redi at gcc dot gnu.org 2020-11-27 14:32 ` redi at gcc dot gnu.org 2021-02-10 16:57 ` cvs-commit at gcc dot gnu.org 2021-02-12 15:50 ` cvs-commit at gcc dot gnu.org 2021-03-29 20:02 ` cvs-commit at gcc dot gnu.org 2021-03-29 20:02 ` cvs-commit at gcc dot gnu.org 2021-03-29 20:05 ` redi at gcc dot gnu.org 2021-06-01 8:12 ` rguenth at gcc dot gnu.org 2021-08-02 15:58 ` cvs-commit at gcc dot gnu.org 2021-08-02 15:58 ` cvs-commit at gcc dot gnu.org 2021-08-02 15:58 ` redi at gcc dot gnu.org 2022-06-30 13:16 ` cvs-commit at gcc dot gnu.org [this message] 2022-07-21 11:16 ` cvs-commit at gcc dot gnu.org 2022-07-22 7:07 ` cvs-commit 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-88881-4-BJUnMlRczn@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).