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++/99290] std::filesystem::copy does not always report errors for recursion Date: Thu, 28 Apr 2022 17:04:46 +0000 [thread overview] Message-ID: <bug-99290-4-VW9zw5KzR5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99290-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99290 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:9821d286bce3edf1d36168f129bfc7fe99c15fc3 commit r11-9948-g9821d286bce3edf1d36168f129bfc7fe99c15fc3 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Apr 28 13:06:31 2022 +0100 libstdc++: Fix error reporting in filesystem::copy [PR99290] The recursive calls to filesystem::copy should stop if any of them reports an error. libstdc++-v3/ChangeLog: PR libstdc++/99290 * src/c++17/fs_ops.cc (fs::copy): Pass error_code to directory_iterator constructor, and check on each iteration. * src/filesystem/ops.cc (fs::copy): Likewise. * testsuite/27_io/filesystem/operations/copy.cc: Check for errors during recursion. * testsuite/experimental/filesystem/operations/copy.cc: Likewise. (cherry picked from commit 4e117418fb71f508c479e0144500f4da9cc92520)
next prev parent reply other threads:[~2022-04-28 17:04 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-26 15:42 [Bug libstdc++/99290] New: " fabian@ritter-vogt.de 2021-02-26 15:49 ` [Bug libstdc++/99290] " marxin at gcc dot gnu.org 2022-04-28 12:33 ` cvs-commit at gcc dot gnu.org 2022-04-28 13:31 ` redi at gcc dot gnu.org 2022-04-28 17:04 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-28 17:05 ` redi at gcc dot gnu.org 2022-06-14 19:20 ` cvs-commit at gcc dot gnu.org 2022-06-14 19:21 ` 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-99290-4-VW9zw5KzR5@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).