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 c++/93901] [10 Regression] noexcept specifier on ctor does not work with constexpr variable or expression since r10-4394 Date: Thu, 14 May 2020 20:39:29 +0000 [thread overview] Message-ID: <bug-93901-4-kiueBZBtVk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93901-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93901 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:4e1592f8e1d6366699e05c0824fc3dc39ca7314b commit r11-403-g4e1592f8e1d6366699e05c0824fc3dc39ca7314b Author: Jason Merrill <jason@redhat.com> Date: Thu May 14 11:15:27 2020 -0400 c++: Fix deferred noexcept on constructor [PR93901]. My change in r10-4394 to only update clones when we actually instantiate a deferred noexcept-spec broke this because deferred parsing updates the primary function but not the clones. For GCC 10 I just reverted that change; this patch adjusts maybe_instantiate_noexcept to update only the clone passed as the argument. gcc/cp/ChangeLog 2020-05-14 Jason Merrill <jason@redhat.com> PR c++/93901 * pt.c (maybe_instantiate_noexcept): Change clone handling.
prev parent reply other threads:[~2020-05-14 20:39 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93901-4@http.gcc.gnu.org/bugzilla/> 2020-03-10 20:49 ` jason at gcc dot gnu.org 2020-03-11 2:02 ` jason at gcc dot gnu.org 2020-03-11 6:54 ` jakub at gcc dot gnu.org 2020-03-17 3:46 ` cvs-commit at gcc dot gnu.org 2020-05-14 20:39 ` cvs-commit at gcc dot gnu.org [this message]
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-93901-4-kiueBZBtVk@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).