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++/97731] terminate called in std::experimental::filesystem::recursive_directory_iterator
Date: Tue, 01 Feb 2022 21:58:55 +0000	[thread overview]
Message-ID: <bug-97731-4-Sy9GMOd3NU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97731-4@http.gcc.gnu.org/bugzilla/>

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

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

commit r12-6982-g2dc2f417288d4f0839b4bc01388e676ee343f941
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Feb 1 14:02:56 2022 +0000

    libstdc++: Add more tests for filesystem directory iterators

    The PR 97731 test was added to verify a fix to the Filesystem TS code,
    but we should also have the same test to avoid similar regressions in
    the C++17 std::filesystem code.

    Also add tests for directory_options::follow_directory_symlink

    libstdc++-v3/ChangeLog:

            * testsuite/27_io/filesystem/iterators/97731.cc: New test.
            *
testsuite/27_io/filesystem/iterators/recursive_directory_iterator.cc:
            Check follow_directory_symlink option.
            *
testsuite/experimental/filesystem/iterators/recursive_directory_iterator.cc:
            Likewise.

  parent reply	other threads:[~2022-02-01 21:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 13:51 [Bug libstdc++/97731] New: " torsten.hilbrich at secunet dot com
2020-11-05 14:10 ` [Bug libstdc++/97731] " redi at gcc dot gnu.org
2020-11-05 14:14 ` redi at gcc dot gnu.org
2020-11-05 18:01 ` cvs-commit at gcc dot gnu.org
2020-11-05 18:05 ` redi at gcc dot gnu.org
2020-11-09 14:53 ` cvs-commit at gcc dot gnu.org
2020-11-09 15:27 ` cvs-commit at gcc dot gnu.org
2020-11-09 15:29 ` redi at gcc dot gnu.org
2022-02-01 21:58 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-04 11:29 ` 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-97731-4-Sy9GMOd3NU@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).