public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r11-10058] libstdc++: Partially revert r11-9772-g6f8133689f4397 [PR105915] Date: Fri, 10 Jun 2022 13:28:29 +0000 (GMT) [thread overview] Message-ID: <20220610132829.8552D3829BEE@sourceware.org> (raw) https://gcc.gnu.org/g:60c84707034f025de3c8821cc5d6f27ff59143b0 commit r11-10058-g60c84707034f025de3c8821cc5d6f27ff59143b0 Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Jun 10 13:01:16 2022 +0100 libstdc++: Partially revert r11-9772-g6f8133689f4397 [PR105915] The r11-9772-g6f8133689f4397 backport made two changes, but only one was needed on the gcc-11 branch. The other should not have been backported, and causes errors with clang. This removes the unwanted part. libstdc++-v3/ChangeLog: PR libstdc++/105915 * include/experimental/bits/fs_path.h (path::begin, path::end): Remove noexcept from declarations. Diff: --- libstdc++-v3/include/experimental/bits/fs_path.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libstdc++-v3/include/experimental/bits/fs_path.h b/libstdc++-v3/include/experimental/bits/fs_path.h index 1cc1b3bf686..a2bc931c696 100644 --- a/libstdc++-v3/include/experimental/bits/fs_path.h +++ b/libstdc++-v3/include/experimental/bits/fs_path.h @@ -425,8 +425,8 @@ namespace __detail class iterator; typedef iterator const_iterator; - iterator begin() const noexcept; - iterator end() const noexcept; + iterator begin() const; + iterator end() const; /// @cond undocumented // Create a basic_string by reading until a null character.
reply other threads:[~2022-06-10 13:28 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220610132829.8552D3829BEE@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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).