public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "oliver.rosten at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108974] New: std::barrier except completion function which is not manifestly noexcept Date: Tue, 28 Feb 2023 19:23:32 +0000 [thread overview] Message-ID: <bug-108974-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108974 Bug ID: 108974 Summary: std::barrier except completion function which is not manifestly noexcept Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: oliver.rosten at googlemail dot com Target Milestone: --- std::barrier<std::function<void()>> b{1, [](){}}; is accepted by gcc (and clang). However, it fails on MSVC - as I think it should - since std::function's call operator isn't manifestly noexcept. https://godbolt.org/z/7vfoa1qhn
next reply other threads:[~2023-02-28 19:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-28 19:23 oliver.rosten at googlemail dot com [this message] 2023-02-28 19:24 ` [Bug libstdc++/108974] " pinskia at gcc dot gnu.org 2023-02-28 21:16 ` redi at gcc dot gnu.org 2023-02-28 21:17 ` redi at gcc dot gnu.org 2023-03-02 2:27 ` de34 at live dot cn 2023-03-02 2:38 ` rodgertq at gcc dot gnu.org 2023-03-02 2:43 ` rodgertq at gcc dot gnu.org 2023-03-02 9:58 ` 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-108974-4@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).