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++/107814] [10 regression] experimental/filesystem/iterators/error_reporting.cc FAILs Date: Thu, 27 Apr 2023 20:08:37 +0000 [thread overview] Message-ID: <bug-107814-4-6sfFDNayWW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107814-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107814 --- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:5d572ffe2e05dbe44edaf19fa10ef2ca3ae8227c commit r10-11315-g5d572ffe2e05dbe44edaf19fa10ef2ca3ae8227c Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Nov 22 19:15:53 2022 +0000 libstdc++: Fix unsafe use of dirent::d_name [PR107814] Copy the fix for PR 104731 to the equivalent experimental::filesystem test. libstdc++-v3/ChangeLog: PR libstdc++/107814 * testsuite/experimental/filesystem/iterators/error_reporting.cc: Use a static buffer with space after it. (cherry picked from commit 1cac00d013856fea4cee0f13c4959c8e21afd2d9)
next prev parent reply other threads:[~2023-04-27 20:08 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-22 13:32 [Bug libstdc++/107814] New: [13 " ro at gcc dot gnu.org 2022-11-22 13:32 ` [Bug libstdc++/107814] " ro at gcc dot gnu.org 2022-11-22 13:35 ` redi at gcc dot gnu.org 2022-11-22 21:42 ` redi at gcc dot gnu.org 2022-11-23 10:05 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-11-23 10:07 ` redi at gcc dot gnu.org 2022-11-23 10:08 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-11-23 10:10 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-11-23 10:19 ` redi at gcc dot gnu.org 2022-11-23 10:20 ` cvs-commit at gcc dot gnu.org 2022-11-23 10:22 ` redi at gcc dot gnu.org 2022-12-21 9:51 ` [Bug libstdc++/107814] [10/11/12 " rguenth at gcc dot gnu.org 2022-12-21 11:37 ` cvs-commit at gcc dot gnu.org 2022-12-22 11:45 ` [Bug libstdc++/107814] [10/11 " cvs-commit at gcc dot gnu.org 2023-04-27 20:08 ` cvs-commit at gcc dot gnu.org [this message] 2023-04-27 20:10 ` [Bug libstdc++/107814] [10 " 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-107814-4-6sfFDNayWW@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).