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++/102499] [12 Regression] Noexcept not matching for std::filesystem::path. Compilation fails for clang
Date: Tue, 28 Sep 2021 17:08:01 +0000 [thread overview]
Message-ID: <bug-102499-4-cE7sJdq2br@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102499-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102499
--- Comment #5 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:f2b7f56a15d9cbbd2f0db22e0e39c4dd161bab69
commit r12-3930-gf2b7f56a15d9cbbd2f0db22e0e39c4dd161bab69
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Mon Sep 27 22:07:12 2021 +0100
libstdc++: Fix mismatched noexcept-specifiers in filesystem::path
[PR102499]
Signed-off-by: Jonathan Wakely <jwakely@redhat.com>
libstdc++-v3/ChangeLog:
PR libstdc++/102499
* include/bits/fs_path.h (path::begin, path::end): Add noexcept
to declarations, to match definitions.
next prev parent reply other threads:[~2021-09-28 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 15:58 [Bug libstdc++/102499] New: Noexcept not matching fgor " unlvsur at live dot com
2021-09-27 16:03 ` [Bug libstdc++/102499] " unlvsur at live dot com
2021-09-27 21:08 ` [Bug libstdc++/102499] Noexcept not matching for " redi at gcc dot gnu.org
2021-09-27 21:09 ` [Bug libstdc++/102499] [12 Regression] " redi at gcc dot gnu.org
2021-09-27 23:24 ` unlvsur at live dot com
2021-09-27 23:59 ` redi at gcc dot gnu.org
2021-09-28 0:07 ` unlvsur at live dot com
2021-09-28 17:08 ` cvs-commit at gcc dot gnu.org [this message]
2021-09-28 17: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-102499-4-cE7sJdq2br@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).