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++/99021] coroutine_handle<_Promise>::from_address() should be noexcept Date: Tue, 09 Feb 2021 14:26:23 +0000 [thread overview] Message-ID: <bug-99021-4-1sBgznGvzg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99021-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99021 --- Comment #4 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:fa183497cf25b604f5b76bc16766f30f5ec7e05b commit r10-9353-gfa183497cf25b604f5b76bc16766f30f5ec7e05b Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Feb 9 11:23:29 2021 +0000 libstdc++: Make coroutine_handle<_Promise>::from_address() noexcept [PR 99021] The coroutine_handle<void>::from_address(void*) version is already noexcept, and they do the same thing. Make them consistent. libstdc++-v3/ChangeLog: PR libstdc++/99021 * include/std/coroutine (coroutine_handle<P>::from_address): Add noexcept. (cherry picked from commit 26a3f288f1895a8c061c0458590542a3d2ee796a)
next prev parent reply other threads:[~2021-02-09 14:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-09 10:27 [Bug libstdc++/99021] New: " redbeard0531 at gmail dot com 2021-02-09 10:42 ` [Bug libstdc++/99021] " redbeard0531 at gmail dot com 2021-02-09 12:32 ` cvs-commit at gcc dot gnu.org 2021-02-09 13:42 ` redbeard0531 at gmail dot com 2021-02-09 14:26 ` cvs-commit at gcc dot gnu.org [this message] 2021-02-09 14:44 ` 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-99021-4-1sBgznGvzg@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).